[csswg-drafts] [scroll-animations-1] Consider initial value of auto for view-timeline-inset (#7747)

flackr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [scroll-animations-1] Consider initial value of auto for view-timeline-inset ==
We previously discussed the [scroll-animations-1 view-timeline-inset](https://w3c.github.io/csswg-drafts/scroll-animations-1/#view-timeline-inset) in the [August F2F discussion here](https://github.com/w3c/csswg-drafts/issues/7243#issuecomment-1204110117) and at the time I didn't object to an initial value of 0 based on the understanding that the [default for scroll-padding was to include some overlap](https://github.com/w3c/csswg-drafts/issues/7243#issuecomment-1204110117:~:text=defualt%20in%20browsers%20is%20to%20include%20some%20overlap), so we left it as that. However, looking into this, it seems that the overlap in page-down is not part of [scroll-padding](https://w3c.github.io/csswg-drafts/css-scroll-snap-1/#scroll-padding) but in addition to it, as can be seen on this [demo](https://output.jsbin.com/gewojan) with `scroll-padding: 0px` where page down scrolls 87.5% of the optimal viewing region defined by the 0px scroll-padding.

Given that the default page-down overlap is not part of scroll-padding, and that the default `scroll-padding: auto` is [typically 0 but allowed to avoid obscured fixed position areas](https://w3c.github.io/csswg-drafts/css-scroll-snap-1/#valdef-scroll-padding-auto) I think that we should make `auto` the default for `view-timeline-inset` since most of the time a developer would want to avoid those obscured regions for view timelines as well.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7747 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 15 September 2022 13:34:13 UTC