- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Mar 2022 16:38:56 +0000
- To: public-css-archive@w3.org
> One question is whether they move at all. I think that is the main issue being questioned here. My opinion is that as fixed pos elements do not move with scroll they probably also shouldn't move with overscroll. However, this could make certain kinds of affordances challenging - e.g. if the browser wants to show some information at the top in the "revealed" part of the page the fixed pos elements may occlude this. > The other question is whether that is detectable by the page (e.g. via getBoundingClientRect()). I don't have strong opinions, though it is important that on android we stretch during overscrolling which would be even more awkward to represent. I think overscrolling could be considered purely a UA effect with no developer visible effect - this is what Chrome does right now. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6299#issuecomment-1076516764 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 March 2022 16:38:57 UTC