HTML OVERFLOW SCROLLING EASIER PLUS

The overflow properties are: visible, hidden, scroll or auto. Either Firefox and IE6 displays in an undesirable way or both have problems. Scolling divs in isolation are simple and reliable but the following examples show that when adjacent to other divs with scroll attributes there can be problems. Problems warning: works in some situations or some browsers or needs care to display as you wish OK in Firefox, Safari, Opera, Google Chrome and IE Some of the examples are provided just to show problems, others show solutions that work in most major browsers. Google Chrome is based on the same WebKit engine as Safari. The IE9 & above updates are mainly related to HTML 5 and CSS3 issues and display to a large extent like other main browsers. In general IE7 and IE8 display like Firefox apart from the HTML5 and CSS3 features. View in Firefox, Safari, Opera and IE but IE6 often needs different solutions. Search Scrolling divs and overflow: hidden

HTML OVERFLOW SCROLLING EASIER PLUS

florian: plus get several years of non-interop. fantasai: this seems like a good idea, but since we have interop on current behavior and it's not too bad, don't htink it's worth implementing the change even if it doesnt' cause webcompat issues I think Tab was talking about Chromium's kBodyScrollsInAdditionToViewport use counter. Rossen_: without that data, seems high risk for low benefit Rossen_: we can close this as by design for now, and if anyone wants to fetch data to show that this design is bad and it is easy and low-risk to change Rossen_: compared to minimum benefit that we get Rossen_: I'm hearing most people align with worry of compat risks emilio: case of overflow:auto on the root and overflow:hidden on the body to clip that. emilio: if it helps authors, maybe then worth doing emilio: Agree with heycam that this doesn't seem hard, but it's not much of a simplification also doesn't seem like a big enough simplification to warrant the risk TabAtkins: can't do that due to HTML parser, unless you're injecting via script

TabAtkins: what content would you put outside the body? TabAtkins: I can't see any way for the page to be depending on this florian: but would have to fetch data to prove it florian: optimistically, might be possible TabAtkins: Do we have usage numbers on overflow on both html and body? florian: question is to ask WG whether it wants to try to make such a change florian: so there's a compat risk to changing florian: but the current behavior has been interop for a long time florian: maybe it's better to just accept one of these two values, whichever is not visible florian: person filing issue suggests that's not very helpful florian: If both are scrollable, we get two scrollbars florian: if it's visible, we propagate from body florian: If html has a value other than visible, we propagate that Topic: Nested scrollers for HTML and BODY RESOLVED: close no change, until time machine.The CSS Working Group just discussed Nested scrollers for HTML and BODY, and agreed to the following: Is there any use for this behavior, or should be simplified? This further clarified in cssom-view and is the current behavior in both chrome and firefox as confirmed by, which produces two sets of scrollbars. The element from which the value is propagated must then have a used overflow value of visible. However, when the root element is an html element (including XML syntax for HTML) whose overflow value is visible (in both axes), and that element has a body element as a child, user agents must instead apply the overflow-* values of the first such child element to the viewport. UAs must apply the overflow-* values set on the root element to the viewport. This is currently the case in css-overflow-3 which says that We could potentially simplify things by saying that overflow applied to body ALWAYS applies to the viewport. Let's explore whether this behavior is really necessary for web compatibility. This is widely supported, but can be a little confusing.

The CSS spec says that 'html ' is special - in that case body actually get's its own scrolling box independent from the viewport.

Html overflow scrolling easier