- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2024 18:27:30 +0000
- To: public-css-archive@w3.org
> > I'm sure there's a lot of important details missing here, but it might be useful to have something written down to point to and work out the details over PRs and issues. WDYT? > > I agree, but the plan was to put it into Overflow L5 along with the current fragmentation appendix, not to patch Overflow L4. :) [#9745 (comment)](https://github.com/w3c/csswg-drafts/issues/9745#issuecomment-1944824869) Sorry about that, this was me misreading the resolution notes. I've created css-overflow-5, moving the fragmentation appendix as we agreed, and moved this over there. > Wrt the content of this, I think it needs more explanation of the use cases it's trying to solve (and the use case it's not trying to solve). For my part, I don't understand why we aren't trying to solve the "highlight the relevant table of contents entry" item along with this, for example. We are. The `scroll-marker` for the current item can be styled with `:checked`: https://github.com/w3c/csswg-drafts/pull/10243/files#diff-fdbff78a41c06b32b51fc29f900df82da5efa11aa9e2e3394047d39c889569f9R896 > The part about only the currently-active scroll marker being focusable is also weird. How do you activate a scroll marker control with the keyboard if it's not focusable? The current algorithm will always produce a selected marker: https://github.com/w3c/csswg-drafts/pull/10243/files#diff-fdbff78a41c06b32b51fc29f900df82da5efa11aa9e2e3394047d39c889569f9R932 I agree if there were not an active marker we'd want to do something similar to a radio group where the first one can get focused. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/10243#issuecomment-2161369249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 June 2024 18:27:31 UTC