- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2016 08:02:07 +0000
- To: public-css-archive@w3.org
Whether or not something needs a scrollbar to show up when there's overflow is something you need to decide on an element per element basis. What that scrollbar should look like is something that you may sometimes want to decide on an element per element basis, but you may also want to make page-wide (or widget-wide, or component-wide... .i.e non local) decisions, and that's a lot easier to do if they cascade separately. And it gives better fallback behavior when some values are not supported: `auto` is a better fallback from `stable` than `visible`, which is what you'd get if you're not careful. Based on that, I think that it makes sense for the values we are discussing now to be in a different property than the choice between `visible` vs `auto`. By that logic, it could make sense for the choice of `scroll` vs `auto` to be in that same other property as well, but too late for that. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/92#issuecomment-252840478 using your GitHub account
Received on Tuesday, 11 October 2016 08:02:23 UTC