- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Feb 2021 19:51:10 +0000
- To: public-css-archive@w3.org
> What's the use case for applying this property on non-scrollable boxes? As stated a few comments back: > The reason for this is to be able to align content outside of a scrolling box (header, toolbar...) with content inside of it. It also lets you keep a stable layout if your app can switch a box from being non-scrollable to scrollable for some reason. (For example, having an editable area initially be inert and overflow:hidden, then switch overflow:auto when activated. Possible use-case: GitHub diff displays when you have lots of files in the diff.) --- > I think instead of playing whackamole with all different layout types there are this property should not only apply to scrollable boxes. We do need to exclude non-replaced inlines, but that's all the whackamole that we could possibly have. Scrollbars aren't something special-cased across display modes. I think the property should just be clarified to "all elements capable of displaying scrollbars", perhaps with this detailed in prose to mean anything that *will* display a scrollbar if set to `overflow:scroll`. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6028#issuecomment-786859702 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 February 2021 19:51:12 UTC