Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS Overscroll Fixed Elements #643

Closed
bmathwig opened this issue May 27, 2022 · 2 comments
Closed

CSS Overscroll Fixed Elements #643

bmathwig opened this issue May 27, 2022 · 2 comments

Comments

@bmathwig
Copy link

Request for Mozilla Position on an Emerging Web Specification

  • Specification Title: CSS Overscroll
  • Specification or proposal URL: https://drafts.csswg.org/css-overscroll/
  • Caniuse.com URL (optional):
  • Bugzilla URL (optional):
  • Mozillians who can provide input (optional):

Other information

Regarding resolution of [css-overscroll] Whether to move position:fixed elements during overscrolling:

  • RESOLVED: fixed-position elements whose scroller is not their containing block do not participate in overscroll
  • RESOLVED: the former statement also applies to sticky element when stuck

We like to get an official position on the resolution to add a note about behavior to the specification.

Chromium Intent to Ship:
https://groups.google.com/a/chromium.org/g/blink-dev/c/ldUEhY-C3OE

Mozilla Bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1760368

@theres-waldo
Copy link

As an engineer working on the relevant code areas of Firefox, the resolution of this issue seems reasonable to me. We have recently implemented this for position:fixed in https://bugzilla.mozilla.org/show_bug.cgi?id=1760368, and have https://bugzilla.mozilla.org/show_bug.cgi?id=1772626 on file for position:sticky.

One edge case that came up during the implementation that doesn't work correctly in Firefox is interacting with content is that "revealed" by an overscroll effect causing it to e.g. slide out from under a fixed element. Not sure if this is worth filing a spec issue about (I think the intent is clear that such areas should be interactable?) but due to the increased implementation complexity we are treating this as an edge case with lower priority.

cc @dlrobertson

@dholbert
Copy link
Contributor

dholbert commented Jun 6, 2022

We should mark this as "worth prototyping", given that we're clearly already prototyping it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants