W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2017

Re: [csswg-drafts] [cssom-view] New feature - scroll-boundary-behavior (an extension of -ms-scroll-chaining)

From: Majid Valipour via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 Oct 2017 20:21:40 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-337027057-1508185298-sysbot+gh@w3.org>
I filed for TAG review for this API and here is the full [feedback](https://github.com/w3ctag/design-reviews/issues/193#issuecomment-332547145). 

One of the feedback items which I am not fully sure about is whether this should be part of the `overflow` property as opposed to being a new property. TAG was not really sure on either direction. Here is the actual feedback:
 
> Should this be a new property, or should this be a new part of the value on 'overflow'? It wasn't clear to us which is the right thing; in CSS this is often decided by whether the pieces should cascade together or separately.

I am inclined to think it is best if this is a separate property i.e., the current design. I can imagine cases where one component want to control `scroll-boundary-behavior` but not the `overflow` e.g.,  to disable pull-to-refresh one should not need to mess with overflow, or a page that want to do `* {scroll-boundary-behavior: contain}` without changing overflow. Also I feel `scroll-boundary-behavior` play a similar role as `scroll-behavior` so it makes sense to match its behavior and be a separate property. 

I provided a tentative response based on the above. However, if there is anyone here who has a strong opinion one way or another I love to hear it and will reflect that to TAG. Same goes for any other feedback item there.

-- 
GitHub Notification of comment by majido
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/769#issuecomment-337027057 using your GitHub account
Received on Monday, 16 October 2017 20:21:42 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:19 UTC