17076 2012-05-16 10:59:15 +0000 Please clarify how seamless should interact with scrollbars 2012-11-06 02:30:40 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#attr-iframe-seamless P3 normal Unsorted 1 contributor ian eric ian mike ojan contributor oldest_to_newest 67780 0 contributor 2012-05-16 10:59:15 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#attr-iframe-seamless Complete: http://www.whatwg.org/c#attr-iframe-seamless Comment: Please clarify how seamless should interact with scrollbars Posted from: 173.164.128.209 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.3 Safari/536.11 67781 1 eric 2012-05-16 11:02:09 +0000 For example, this section: In visual media, in a CSS-supporting user agent: the user agent must force the height of the initial containing block of the active document of the nested browsing context of the iframe to zero. This is intended to get around the otherwise circular dependency of percentage dimensions that depend on the height of the containing block, thus affecting the height of the document's bounding box, thus affecting the height of the viewport, thus affecting the size of the initial containing block. This would cause user agents to add scrollbars in their initial computation, since the containing block starts at 0px, no? Similarly, what about child documents in quirks mode? There the body/html are expected to fit to the viewport size? For now in WebKit I've disabled this quirk when the document is seamless, but that doesn't feel 100% right. Some explanation of how the scrollbar negotiation should work would be helpful. :) Presumably it should work exactly as <div style="scroll: auto"> would, but it's a bit tricky due to the assumption of html/body as being the root (at least in the code). Presumably we should treat html/body as just normal blocks inside the seamless iframe block. 67784 2 zcorpan 2012-05-16 13:01:07 +0000 > Similarly, what about child documents in quirks mode? There the body/html are > expected to fit to the viewport size? That's not expected. It's what WebKit does, but Opera and Gecko don't. I'm not sure, but I think IE9 in non-compat-view quirks mode also doesn't. The quirks mode spec specifies the Opera/Gecko behavior. http://simon.html5.org/specs/quirks-mode#the-percentage-height-calculation-quirk 70811 3 contributor 2012-07-18 17:32:10 +0000 This bug was cloned to create bug 18172 as part of operation convergence. 73202 4 ian 2012-09-04 22:01:03 +0000 Where would the scroll bars come in? Do you have an example? 77929 5 ian 2012-11-06 02:30:40 +0000 eseidel: ping. I don't understand this bug.