scroll-initial-target

[DavMila]

Request for Mozilla Position on an Emerging Web Specification

• Specification title: scroll-initial-target
• Specification or proposal URL (if available): https://drafts.csswg.org/css-scroll-snap-2/#scroll-initial-target
• Explainer URL (if available): https://github.com/DavMila/explainer-scroll-initial-target
• Proposal author(s) (@-mention GitHub accounts): @DavMila @argyleink

[DavMila]

Just a quick update here:

• the CSS working group resolved to use scroll-initial-target instead of scroll-start-target and nearest instead of auto

per TAG feedback.

[emilio]

@hiikezoe, any concern with this?

[hiikezoe]

I don't see any big concerns right now. There are several things are not very clear to me in the current spec.

1. Does scroll-snap win over scroll-initial-target? (I guess so)
2. Does restoring scroll position feature while being reloaded contents by browser win? (I don't think so)
3. Should scroll-padding and scroll-margin be respected for scroll-initial-target?
4. Once after a scroll-initial-target element has been settled, then if the element position is changed for some reasons, an extreme case is the element is animated by CSS transform change, browser needs to re-evaluate the scroll position? It's a role of scroll anchoring? what if overflow-anchor: none is specified?
5. Similar to above, what if the scroll-initial-target element is also a target of scroll driven animation?
6. What if the scroll-initial-target element is a position:sticky element? Say, position: sticky; top: 20px or some such, browser just needs to scroll the position where the sticky element was originally laid out?

Anyways, the basic concept looks reasonable and nice to me.