- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 May 2012 11:02:09 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17076
Eric Seidel <eric@webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eric@webkit.org,
| |ojan@chromium.org
--- Comment #1 from Eric Seidel <eric@webkit.org> 2012-05-16 11:02:09 UTC ---
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.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 16 May 2012 11:02:16 UTC