Skip to content

[css-overscroll-1] Should overscroll-behavior change the behavior of a subframe? #5129

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

Open
smfr opened this issue May 28, 2020 · 2 comments

Comments

@smfr
Copy link
Contributor

smfr commented May 28, 2020

https://drafts.csswg.org/css-overscroll

Should overscroll-behavior change the behavior of a (possible cross-origin) subframe? This seems like leakage of CSS through frame boundaries, which isn't something we normally do.

@fred-wang
Copy link

I think @smfr has been confused by my (probably incorrect) initial WebKit's patch and testcase at https://bugs.webkit.org/show_bug.cgi?id=176454 where I used something like <iframe style="overscroll-behavior: none">

Reading the current overscroll-behavior spec, overscroll-behavior only applies to scroll containers (https://drafts.csswg.org/css-overflow-3/#scroll-container i.e. have scroll overflow as specified by overflow-x/overflow-y). So I don't think overscroll-behavior applies to iframe.

I think it would be consistent with scroll-behavior here, which applies to scrolling boxes ( https://drafts.csswg.org/cssom-view/#scrolling-box ) instead and says " When this property is specified on the root element, it applies to the viewport instead.".

See also the related #2977 about whether the property should be read on the root element or on the scrolling element. This only matters for quirks mode.

@hiikezoe
Copy link

We have encountered a similar issue, in our case the iframe document element has "overscroll-behavior-y: none" but the iframe document in question is not scrollable at all. In such cases whether the overscroll-behavior property should be respected or not? Chrome appears not respecting it, whereas Firefox does as of now.

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

3 participants