Closed
Bug 242645
Opened 20 years ago
Closed 6 years ago
*|*:root; 'overflow' property should not be applied to the viewport
Categories
(Core :: Layout, enhancement)
Core
Layout
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: annevk, Unassigned)
References
()
Details
(Keywords: css2, testcase)
Attachments
(1 file)
208 bytes,
application/xml
|
Details |
See also bug 230554 comment 6. Note that we currently do not apply 'overflow' from xhtml|body to the viewport (and that is correct): http://annevankesteren.nl/test/css/p/overflow/xhtml-body.xml The URL works correctly in Opera 7.5p3.
Comment 1•20 years ago
|
||
Ian, this seems like your sort of thing to QA.... What is the spec likely to end up saying about this issue?
QA Contact: core.layout → ian
Comment 2•20 years ago
|
||
It's likely to say "@viewport allows..." etc.
Reporter | ||
Comment 3•20 years ago
|
||
This may end up being INVALID. Together with bug 242646. The CSS WG seems to have changed the plan of action again.
Comment 4•20 years ago
|
||
Well if browsers implemented what the specs said in the first place, we wouldn't have to _change the spec_ to match what was interoperably implemented. :-P
Reporter | ||
Comment 5•19 years ago
|
||
Although this bug may be invalid. We are not setting |overflow| to the viewport at the moment. Somehow we set the scrollbar to the viewport but make it relate to the width of the HTML element. See the testcase for a simple example.
Reporter | ||
Comment 6•19 years ago
|
||
I meant of course, root element.
Reporter | ||
Comment 7•19 years ago
|
||
(In reply to comment #4) > Well if browsers implemented what the specs said in the first place, we wouldn't > have to _change the spec_ to match what was interoperably implemented. :-P Opera actually applies 'overflow' directly to the root element. I just tested it with the attached testcase. The CSS WG must have been testing something different I guess. (There is no interoperable implementation here.)
Updated•15 years ago
|
QA Contact: ian → layout
Reporter | ||
Comment 8•6 years ago
|
||
This got fixed at some point.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•