absolutely positioned child of relative inline containing block is positioned relative to only first line of inline
Categories
(Core :: Layout: Positioned, defect)
Tracking
()
Webcompat Priority | P3 |
People
(Reporter: rn214, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: parity-chrome)
Attachments
(3 files)
Reporter | ||
Comment 1•16 years ago
|
||
Updated•16 years ago
|
Reporter | ||
Comment 3•16 years ago
|
||
Comment 4•16 years ago
|
||
Comment 5•16 years ago
|
||
Comment 6•16 years ago
|
||
Updated•16 years ago
|
Updated•16 years ago
|
Comment 7•16 years ago
|
||
Updated•14 years ago
|
Comment 9•14 years ago
|
||
Comment 10•11 years ago
|
||
Comment 11•10 years ago
|
||
Comment 12•9 years ago
|
||
Comment 14•8 years ago
|
||
Comment 15•8 years ago
|
||
Comment 18•8 years ago
|
||
Comment 20•7 years ago
|
||
Comment 21•7 years ago
|
||
Comment 22•7 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 25•4 years ago
|
||
The relevant spec text is in css-position-3.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Comment 27•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 8 duplicates.
:dholbert, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 28•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Comment 29•2 years ago
|
||
We have these 2 tests (Ahem font must be installed on your system)
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/containing-block-031.html
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/containing-block-032.html
that can be adjusted to be submitted to WPT once Issue 8284 https://github.com/w3c/csswg-drafts/issues/8284 is resolved.
[Edit]
I am really eager to submit these because we have been keeping these for over 13 years now:
https://lists.w3.org/Archives/Public/public-css-testsuite/2010Jul/0046.html
[/Edit]
I think bug 489207 and bug 743599 should be resolved as DUPLICATEs.
Comment 30•2 years ago
|
||
Thanks. And yeah, let's implement whatever behavior shakes out of that spec issue (being discussed in the CSSWG meeting right now).
Updated•2 years ago
|
Comment 33•2 years ago
|
||
CSSWG resolution:
RESOLVED: in LTR-tb the top-left corner is the top-left corner of the top-left-most fragment of the first line, and the bottom and right edges are bottommost and rightmost edges of all the fragments. Directionality comes from the inline
(with analogous writing-mode-informed directions for other direction/writing-mode setups. As noted at the end of the resolution, the direction/writing-mode of the inline element, i.e. the thing forming the abspos containing block, is what matters.)
Description
•