- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Mar 2025 17:07:09 +0000
- To: public-css-archive@w3.org
Wrote this [code snippet](https://codepen.io/rachelandrew/pen/QwWZygJ/8605fed5084835623bb90799ea7e6972) to test it out. Both the text selection and the caret navigation follow the DOM order on all browsers. Neither `order` nor `tabindex` affect the text/caret selection. It would be really tricky to implement this behavior based on reading-flow. It wouldn't be a case of re-ordering the sibling children of a specific container anymore. And how are we meant to interpret the different reading-flow keyword values? -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12014#issuecomment-2761946484 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 March 2025 17:07:10 UTC