-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selection #2
Comments
Please let me know if the summary as written isn't right, doesn't cover something important, or covers something it shouldn't. |
WICG/webcomponents#79 seems to be the shadow root selection issue. The last action was @mfreed7 suggesting that they were planning to look at putting up spec PRs early/mid 2022. Unless there's a significant change in the status there I'd propose we make those PRs and some accompnying tests part of the concrete goals for this effort. |
Note, the Intl.Segmenter is a very good way to get "legitimate" caret locations within a string (e.g., keeps grapheme clusters together, also helps with "word" navigation). |
Selection tests have been submitted here: web-platform-tests/wpt#35862 |
So we have a test PR, with some feedback. Do we believe that merging that PR completes all the selection work we were hoping to achieve as part of this investigation? |
As far as I can tell, the issues addressed in this PR do in fact correspond to the main selection issues editors are currently having. I have not received any feedback from other editors to the contrary either. |
Updating the score here to 50% per the meeting. |
Next step is review of the test PR; if that lands then this area will be complete. |
The test PR landed, so I propose we score this as 100%. |
Selection, including where it's possible to put the caret, is an area that's been identified as high impact for editor authors. In particular the following questions:
For the caret position, we have some existing spec text that calls out some special cases: https://github.com/w3c/contentEditable/blob/ba10fb177f68567ff742d0acb6caab337224af2d/index.html#L145-L187
So as part of this investigation we should:
The aim is that the identified tests would be a candidate for an Interop 2023 focus area that browsers would be able to commit to.
The text was updated successfully, but these errors were encountered: