You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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].
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 ofoverscroll-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 byoverscroll-behavior: none
?@majido
The text was updated successfully, but these errors were encountered: