Bug 74148
| Summary: | fast/css/parsing-css-block.html fails | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, annevk, darin, koivisto, macpherson, ntim, simon.fraser, szledan, zherczeg |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 72360 | ||
| Bug Blocks: | 69083 | ||
Ryosuke Niwa
The test added by https://bugs.webkit.org/show_bug.cgi?id=72360 has a failing expectation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Zoltan Herczeg
We had a discussion about the test expectations, and the conclusion was that even failing tests has their purpose, since they show the current behaviour (for example, you would otherwise never know about this issue).
Ryosuke Niwa
(In reply to comment #1)
> We had a discussion about the test expectations, and the conclusion was that even failing tests has their purpose, since they show the current behaviour (for example, you would otherwise never know about this issue).
Sure. But we should fix this bug.
Alexey Proskuryakov
Is this test correct? Firefox also says FAILURE.
Ahmad Saleem
Still has failure expectation - https://searchfox.org/wubkat/rev/273f22582ad8144106018a89f5c85f1d15da0253/LayoutTests/fast/css/parsing-css-block-expected.txt
Do we need to do anything here?
Anne van Kesteren
If the test fails across Chromium and Gecko too, we should probably flip the passing condition of the test.