[csswg-drafts] [css-scroll-snap-1] Drop 'scroll-padding: auto'? (#12943)

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

== [css-scroll-snap-1] Drop 'scroll-padding: auto'? ==
It's not clear to me that implementations are doing anything particularly interesting with the initial value of `scroll-padding`, `auto`. Certainly it's not [automatically avoiding sticky headers](https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%3B%20height%3A%20100px%3B%20overflow%3A%20scroll%22%3E%0A%3Cdiv%20style%3D%22background%3A%20orange%3B%20position%3A%20sticky%3B%20top%3A%200%22%3Esticky%3C%2Fdiv%3E%0A%3Ca%20href%3D%22%22%20style%3D%22margin-top%3A%20200px%3B%20background%3A%20aqua%3Bdisplay%3A%20block%22%3Ethis%3C%2Fa%3E%0A%3Ca%20href%3D%22%22%20style%3D%22margin-bottom%3A%20200px%3B%20background%3A%20aqua%3Bdisplay%3A%20block%22%3Ethat%3C%2Fa%3E)...

Should we drop this value and set the initial value to `0`? And maybe consider adding it back as a non-initial value that does something useful and automatic?

FWIW, the initial value had two purposes:
- Reflect the amount of default overlap between paging operations / default spacing around scroll-into-view operations so that authors could then control it explicitly by setting a different value. (If we want this, maybe we can call it `normal`.)
- Try to heuristically account for fixed headers/footers that obscure the content.

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


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

Received on Monday, 13 October 2025 20:59:41 UTC