Text input should still be possible through EditContext when another element is selected but not focused
Categories
(Core :: DOM: Editor, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: ltenenbaum, Assigned: ltenenbaum)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
I am thinking that for canvas-based EditContext to be accessible, it will be necessary to keep the selection in the EditContext in sync with the selection in the DOM fallback content, as demonstrated in the attached file. However, we don't allow text input if the selection is outside of the EditContext associated element.
(It's possible that this causes issues even with DOM-based EditContext, so I'll mark this as blocking bug 2046107.)
| Assignee | ||
Comment 1•1 month ago
•
|
||
Although, perhaps we shouldn't accept text input for DOM-based EditContext when the selection is somewhere else, since the DOM selection is supposed to correspond to the selection in the EditContext.
Edit: Chrome does accept input for DOM-based EditContext even if the selection is somewhere else, so let's follow that.
| Assignee | ||
Comment 2•28 days ago
|
||
Oh hmm no, Chrome actually just forces the selection to stay in the DOM EditContext, even if it's changed by the Selection API. So it's fine to handle this for canvas only.
| Assignee | ||
Comment 3•28 days ago
|
||
No, that's wrong, Chrome does allow the selection to go outside, but it doesn't render the caret, even if caret browsing is enabled.
| Assignee | ||
Comment 4•28 days ago
|
||
| Assignee | ||
Comment 5•28 days ago
|
||
https://ltenmoz.github.io/editcontext-canvas/index.html is a more fleshed-out editor than the one attached here.
| Assignee | ||
Updated•28 days ago
|
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/61576 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Updated•4 days ago
|
Description
•