- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Jul 2018 19:51:57 +0000
- To: public-css-archive@w3.org
> Firefox's approach has benefits in that it fixes the problem scroll-padding aims to solve on already-existing websites. Therefore it might be beneficial for other browsers to do similarly.
Perhaps it is beneficial for other browsers to implement this. But that is not something that we need to spec but rather an optimization that each browser can decide on. Similar to how the actual amount that implementations consider a "page" is implementation specific.
More concretely, Firefox detection is based on a heuristic with many caveats. I don't think we should specify anything like that.
The good news is that now their behavior can be described based on the new concept ('scroll port viewing region'?) introduced in the specification. Perhaps we can/should add a note that implementations are allowed to adjust scroll port viewing region if there is not user specified `scroll-padding`.
> However, this could result in clashes when scroll-padding is used in a stylesheet on a website the browser has detected as using a fixed header and has already applied an offset to.
I think this will be a bug for browsers that have additional heuristics. In particular, if authors have
specified a `scroll-padding` the browser should not employ additional heuristics. See my suggestion above to add a note that should clarify this.
--
GitHub Notification of comment by majido
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2929#issuecomment-406394051 using your GitHub account
Received on Thursday, 19 July 2018 19:52:00 UTC