[WPT] css/css-transforms/preserve-3d-flat-grouping-properties-containing-block.tentative.html fails
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: gerchiko, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4414.0 Safari/537.36 Edg/90.0.801.0
Corresponding crbug: https://bugs.chromium.org/p/chromium/issues/detail?id=1008483
|
||
Comment 2•5 years ago
|
||
Hey gerchiko,
Can you give us a little more steps about this issue?
The test fails in WPT:
https://wpt.fyi/results/css/css-transforms/preserve-3d-flat-grouping-properties-containing-block.tentative.html?label=master&label=experimental&aligned
I looked more at this test and apparently the test is written wrong.
I raised Chromium bug to fix the test: https://bugs.chromium.org/p/chromium/issues/detail?id=1181767.
In Chrome, the fixed test still fails due to the feature not being implemented: https://bugs.chromium.org/p/chromium/issues/detail?id=1008483.
I can update status of this bug once the test is fixed in Chrome and the changes propagate to WPT.
|
||
Comment 4•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::CSS Parsing and Computation' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 5•5 years ago
|
||
(In reply to gerchiko from comment #3)
The test fails in WPT:
https://wpt.fyi/results/css/css-transforms/preserve-3d-flat-grouping-properties-containing-block.tentative.html?label=master&label=experimental&aligned
Request: for subsequent "some WPT test fails" bugs, it'd be great if you could include that wpt.fyi link (and/or any context about the failure, e.g. the failure text) as part of the initial comment.
I looked more at this test and apparently the test is written wrong.
[...]
I can update status of this bug once the test is fixed in Chrome and the changes propagate to WPT.
Aha, great! Thanks for doing that investigation. Sounds like this has status:INVALID as a Firefox bug, then, since there aren't any changes to be made (aside from an eventual test-sync).
Description
•