New wpt failures from PR 22462: /css/css-flexbox/intrinsic-width-orthogonal-writing-mode.html
Categories
(Core :: Layout: Flexbox, defect, P3)
Tracking
()
People
(Reporter: mozilla.org, Unassigned)
References
Details
(Whiteboard: [wpt])
The following tests have untriaged failures in the CI runs for wpt PR 22462:
New Tests That Don't Pass
/css/css-flexbox/intrinsic-width-orthogonal-writing-mode.html
.inline-flexbox 3: FAIL (Chrome: PASS, Safari: FAIL)
.inline-flexbox 2: FAIL (Chrome: PASS, Safari: FAIL)
These updates will be on mozilla-central once bug 1625104 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Comment 1•5 years ago
|
||
Live test on WPT.fyi:
http://wpt.live/css/css-flexbox/intrinsic-width-orthogonal-writing-mode.html
The failure boils down to this reduced testcase:
data:text/html,<div style="display:inline-flex;border:1px solid black"><div style="writing-mode:vertical-lr">Hello
...which is really just a bug about intrinsic sizing, which reveals itself with inline-block
and float:left
as well:
data:text/html,<div style="display:inline-block;border:1px solid black"><div style="writing-mode:vertical-lr">Hello
data:text/html,<div style="float:left;border:1px solid black"><div style="writing-mode:vertical-lr">Hello
(Firefox renders all of these with a collapsed 0-width black-bordered area, whereas Chrome renders the border around the text correctly.)
This is a version of bug 1473789.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 6•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
Description
•