Skip to content

[css-overscroll-behavior] and users text selection boundary scroll chaining of none value #3394

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
jonjohnjohnson opened this issue Dec 4, 2018 · 1 comment

Comments

@jonjohnjohnson
Copy link

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

It seems to me, in all of my poking and prodding of overscroll-behavior, that whenever an author would want to inhibit scroll chaining, by use of overscroll-behavior: none, they would also want to keep from a users selection of text inside to cause scrolling of any ancestor scrollers. From what I can gather, user-select: contain may have some implications here if it separately covers this case and would require use of both property declarations, or if it's worthwhile to the effect provided only by overscroll-behavior: none?

@majido

@jonjohnjohnson
Copy link
Author

In https://bugs.chromium.org/p/chromium/issues/detail?id=911396#c6 @majido says..

This seems reasonable to me because it seems to me that the selection related scroll can be considered as a single scroll that originated from the element where selection was started. So it falls under what overscroll-behavior controls [1].

[1] https://drafts.csswg.org/css-overscroll-behavior/#valdef-overscroll-behavior-contain
"The user agent must not perform scroll chaining to any ancestors along the scroll chain regardless of whether the scroll originated at this element or one of its descendants."

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

2 participants