Absolutely-positioned element in <ruby> is not shown
Categories
(Core :: Layout: Ruby, defect)
Tracking
()
People
(Reporter: karlcow, Assigned: xidorn)
References
()
Details
Attachments
(3 files)
chrome left, firefox right
following the bug report on https://webcompat.com/issues/53076
And this test:
<div>
<ruby data-ruby="しぶ">澁<rt>しぶ</rt></ruby>
</div>
div {
padding: 5em;
}
[data-ruby] {
position: relative;
}
[data-ruby]::before {
content: attr(data-ruby);
position: absolute;
top: -1em;
left: 0px;
right: 0px;
margin: auto;
font-size: 0.5em;
text-align: center;
background-color: gold;
}
rt {
display: none;
}
as we can see in the screenshot. Chrome displays the characters but not firefox.
|
Reporter | |
Comment 1•4 years ago
|
||
Test case available at https://codepen.io/webcompat/pen/yLYWoNB
|
||
Comment 2•4 years ago
|
||
|
|
||
Updated•4 years ago
|
|
|
||
Comment 3•4 years ago
|
||
::before creates a regular inline box inside the <ruby> box, so it's basically equivalent to using a <span> instead of a ::before pseudo-element, which doesn't show up either.
Xidorn do you know if this is supposed to work per spec?
|
|
||
Comment 4•4 years ago
|
||
Err, see above :)
|
Assignee | |
Comment 5•4 years ago
|
||
That's a very interesting case... I totally have no idea what the site get from doing this :/
Anyway, I don't see why it shouldn't be displayed. I'll have a look this weekend.
|
|
Assignee | |
Updated•4 years ago
|
|
||
Comment 6•4 years ago
|
||
Given that this is confirmed and assigned, I am going to give this an S3 severity.
|
|
Assignee | |
Comment 7•4 years ago
|
||
Pushed by mozilla@upsuper.org: https://hg.mozilla.org/integration/autoland/rev/6bb6a5cdc941 Reflow absolute frames in ruby container and ruby base container. r=dholbert
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/23972 for changes under testing/web-platform/tests
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
Upstream PR was closed without merging
|
||
Comment 12•4 years ago
|
||
Backed out for causing failures at abs-in-ruby-base-container.html
Backout link: https://hg.mozilla.org/integration/autoland/rev/fb5f607b3f90aa0d69d97c456ebc57638b05fca4
Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=6bb6a5cdc941eaa15c0e36dcaf8e4ad8509d4e90&selectedTaskRun=P0vgYmc6QnWgzkZNGBzUIw-0
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=305012494&repo=autoland&lineNumber=3136
|
|
Assignee | |
Comment 13•4 years ago
|
||
I believe the test failure is related to bug 1643868 somehow. I can observe similar issue on Linux, but it happens more consistently on Android for some reason. It's especially interesting that connecting inspector to GeckoView resets the position.
|
||
Comment 14•4 years ago
|
||
Pushed by mozilla@upsuper.org: https://hg.mozilla.org/integration/autoland/rev/2dd4b6b2f0d7 Reflow absolute frames in ruby container and ruby base container. r=dholbert
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
|
||
Comment 16•4 years ago
|
||
| bugherder | ||
Upstream PR merged by moz-wptsync-bot
|
||
Comment 18•4 years ago
|
||
The patch landed in nightly and beta is affected.
:xidorn, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.
For more information, please visit auto_nag documentation.
|
|
Assignee | |
Updated•4 years ago
|
Description
•