Re: [w3ctag/design-reviews] Spec Review for scroll-start-target (Issue #1011)

> 1. Is `scroll-start-target: auto` a developer-friendly way to say "please scroll to me"? I'd expect `auto` to mean "do what the UA thinks is right", which is not the behavior it's currently specified to have. I could imagine `on-first-appearance` being a clearer way to describe what it's asking for. This sort of naming question is firmly within the CSSWG's area of expertise, so there's probably a long discussion thread about it, and I would just benefit from a link to it.

Great point but unfortunately, I'm afraid there isn't a discussion thread I can point to.
I think you are right that this would be a bit of a departure from what `auto` in CSS means. A better keyword might be in order, something like: `on-first-appearance` or `align` or `active` or `visible`. I'll file an issue with the working group.

> 2. https://drafts.csswg.org/css-scroll-snap-2/#scroll-start-target-fragment-navigation says "While the document is being [updated](https://html.spec.whatwg.org/multipage/browsing-the-web.html#updating-the-document) ...". This sort of [COMEFROM](https://en.wikipedia.org/wiki/COMEFROM) statement is out of favor in modern specifications. Can y'all work to add an appropriate hook in HTML?

That seems like a good idea, thanks. I’ll write a PR to add a hook to the HTML spec.

> 3. If a page is slow to load and has multiple `scroll-start-target` elements, it seems like the current definition might cause multiple scrolls, if the UA decides to partially render after getting the initial target. Developers might not see this if they test only on a fast connection, but users on slower devices could wind up with a bad experience. Does something in the definition subtly prevent this? Has the WG discussed how to prevent it?

The spec prioritizes selecting the `scroll-start-target` element which is first in DOM order.
For the UA to select and scroll to a different target, the UA would have to have inserted the late-arriving target into the DOM in a position that is before the position of the already-selected target in DOM order. We think that it isn’t very common for pages to load elements out-of-order and so having multiple `scroll-start-target` elements is not likely to lead to unfriendly jumps.




-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1011#issuecomment-2465250625
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1011/2465250625@github.com>