- From: Mason Freed via GitHub <noreply@w3.org>
- Date: Wed, 10 Dec 2025 17:25:16 +0000
- To: public-css-archive@w3.org
Also see https://github.com/w3c/selection-api/issues/336 Note that for the selection API, "fixing" this might not be straightforward. Selecting a chunk of text that doesn't appear in DOM order means that the browser must support multi-range selection. The [Selection API issue above](https://github.com/w3c/selection-api/issues/336) is about whether the selection API should operate on the flat tree or the composed tree. This issue is, I think, about perhaps changing that to use the layout tree (since that's the visible thing users see and select). That's even more difficult, for the same reasons, plus the added fact that the layout tree isn't 1:1 with the DOM tree. I'm concerned that this is a fairly large can of worms, but I'd love to be proven wrong. Arrow key navigation (for e.g. radio buttons and customizable-select) and caret navigation are likely somewhat easier to fix. I'd agree that it would be good for all of these behaviors (as much as possible) to follow reading-flow/reading-order. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12014#issuecomment-3638168875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 December 2025 17:25:17 UTC