Skip to content

Conversation

@siusin
Copy link
Contributor

@siusin siusin commented Dec 8, 2025

Please review:

Name of the new spec: Caret Movement
Abstract: This specification aims to improve the user experience of Bidirectional text selection in scenarios where LTR and RTL text are both used, as well as in other complex situations such as arrow navigation of the cursor around inline images, and text input within contenteditable elements.

/cc @ragoulik

@siusin siusin requested a review from johanneswilm December 8, 2025 16:04
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.

A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from <span id='cfc'>one week</span>, depending on the chair's evaluation of the group consensus on the issue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@siusin Is it possible to adjust the wording here that a CfC is issued implicitly automatically with every resolution to make it clear that we do not start a separate manual process of issuing a CfC with every resolution?

@johanneswilm
Copy link
Contributor

On the new spec:

TPAC 2025:

support for Bidirectional(presence of both ltr and rtl) text: Selection and cursor navigation – where should we start?
Rakesh
We dont have github issue or proposal for bidirectional support. Still in ideation phase
Concept of proposal - today a common practice for people to use LTR and RTL text in same sentence in same world.
In chromium based browsers, in selection part, it has both combination. We want to improve UX to support such combinations
We plan to have a proposal, don’t have much as of now. Just wanted to pitch the idea
Johannes
We already spoke about making new spec, not much about directions
Caret movement in general is oe of things, close to selection but not the same
There are other questions - editor inside editor does it go around it ? should go in editing spec
Given another issue about caret movement all should go into new spec - with a specific section
We solved it 10 years ago - caret wouldn’t go certain places. It was less of a need. But a spec would be good with new browsers coming along.
Are you proposing a new spec, can we have another section with carent move around svgs, images and other problematic elements
Rakesh
Would be good idea
Johannes
Need a name for spec. - Caret movement spec
Smaug
Sounds reasonable
Rakesh:
Sounds good
Johannes
Resolution - have new spec “Caret movement”. Rakesh will be the editor. I can share more issues around the caret movement. Looking forward for some proposals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants