Open Bug 1650712 Opened 5 years ago Updated 1 year ago

New wpt failures in /css/css-tables/tentative/colspan-redistribution.html

Categories

(Core :: Layout: Tables, defect)

defect

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [wpt])

Syncing wpt PR 23807 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

/css/css-tables/tentative/colspan-redistribution.html
table 12: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1641377 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.

This is in tentative folder, so I assume we don't implement all of these tests.

Severity: -- → S3

We've got a few new failures here, per dupe that I just marked.

Note that the live test has a bunch of red text describing known incompatibilities that the test is triggering, like:

FF, Legacy, and TablesNG all disagree about the correct widths. FF feels more like the right answer, but I can't figure out the math behind it.

and:

In testcase /tables/mozilla_expected_failures/core/col_span2.html distribution right-to-left is described as a bug. Firefox and Edge both distribute left to right. Chrome is only one that distributes right to left. Firefox distribution is not cumulative, it uses original minmax to compute final widths. Edge agrees with TablesNG. But, mozilla is stable for row reordering.

So (on top of the tentative thing), it's pretty clear that this test is more exploratory than authoritative.

You need to log in before you can comment on or make changes to this bug.