+1 this would make scroll up for search or scroll up for nav really easy. These are common patterns in some native apps, for example iOS uses scroll up for search in numerous places.

Hey 👋

In addition to scroll-start where I'm assuming this is short for scroll-start: <scroll-start-x> <scroll-start-y> 😎

Would be great to have keyword values like those used with the Flexbox API ✄1�7

scroll-start: < center | auto | end | start | explicit value >;

ʕ´•ᴥ•`ʔ

Would be great to have keyword values like those used with the Flexbox API ✄1�7

center, start and end added to the explainer! great suggestions thanks!

If this is a < length > value I assume percentages would work and you might not need keywords. Although you could always have both.

I also assume if you set it to a value like 50vh this would scroll down to half the height of the viewport on initial render but not be relative going forward? Similar with percentage values? Or do they remain relative until the scroll is interacted with thus changing the scroll position?

If this is a < length > value I assume percentages would work and you might not need keywords. Although you could always have both.

they're already specced as <length-percentage> 🙂

Or do they remain relative until the scroll is interacted with thus changing the scroll position?

they're active until interacted with yep, at which point they not longer apply. from the explainer "Once the user has interacted with the scroll area, scroll-start and scroll-start-target has no effect. The styles must be present during scrollport creation or they have otherwise missed their timing."

For people who use the keyboard to navigate : would this impact the starting position of the focus ? Otherwise the first time you press TAB you'll be taken back to the beginning of the scroll area.

For people who use the keyboard to navigate : would this impact the starting position of the focus ? Otherwise the first time you press TAB you'll be taken back to the beginning of the scroll area.

Excellent consideration. I imagine a developer using this new prop could/would have already been managing tabindex properly on their markup so tabbing into the (carousel, tabs, testimonials, etc) didnt scroll them to the beginning.

tab/focus management should pair closely with this prop. it'd be a good idea to mention that in the explainer/docs though thanks! 👍🏻