- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2025 18:40:08 +0000
- To: public-css-archive@w3.org
flackr and I talked a bit offline. One idea that Rob had is to only use a deep node anchor for its immediate scroll parent. Then using that scroll parent as the anchor for the next scroll parent and so on (Rob correct me if I'm wrong). All of this started because if we use the cursor there's a weird interaction with `overflow: clip` contenteditable thing that ends up scrolling the document to keep the cursor in place, which feels wrong. I think the solution of scroller anchoring chaining may work but also carries quite a bit of risk, since we haven't yet thought through all of the edge cases involved. Personally, I still prefer the solution of using the priority candidate as the root for the node selection algorithm, instead of just using the priority candidate directly. That seems like a small change and aligns with the scroll anchor algorithm if there was no priority candidate (ie if you remove the focus from the contenteditable field then the behavior you get is the same). So I like that option from the consistency perspective as well. I'm happy to limit this to just contenteditable things or any priority candidate -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11748#issuecomment-2675285643 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 February 2025 18:40:09 UTC