Closed Bug 1871609 Opened 6 months ago Closed 1 month ago

Border-collapsed table's border width recalculation is stateful

Categories

(Core :: Layout: Tables, defect)

defect

Tracking

()

VERIFIED FIXED
127 Branch
Tracking Status
firefox127 --- verified
firefox128 --- verified

People

(Reporter: dshin, Assigned: dshin)

References

Details

Attachments

(2 files)

STR:

  1. Open the testcase
  2. Note table shape
  3. Hover over "one"
  4. Note thick border between "one" and "two"
  5. Hover elsewhere
  6. Note table shape
    Expected: 2) and 6) are identical
    Actual: 6) has more space between "one" and "two"
Severity: -- → S3

Probably happened since bug 1464928. The testcase is derived from a test added from that bug.
The path responsible was added from bug 41262 - stored border widths are stateful, storing the max of the result of GetBorderWidth and the incoming border (Which is 0 in this case). GetBorderWidth returns a halved value, hence why the final table's gap between cells is half of 20px.
The original test case doesn't suffer from this because it works with 1px borders, of which half is rounded down to 0.

Depends on: 1873473
Assignee: nobody → dshin
Status: NEW → ASSIGNED
Pushed by dshin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/84b76f80bf96
On calculating border-collapsed table's borders, reset max-seen width. r=TYLin
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/46138 for changes under testing/web-platform/tests

Backed out for causing wr failures in /css/css-tables/*

Flags: needinfo?(dshin)
Upstream PR was closed without merging

Changes made, try run looks good (Failure cases don't even use table, so it seems unrelated)

Flags: needinfo?(dshin)
Pushed by dshin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/39658819ee60
On calculating border-collapsed table's borders, reset max-seen width. r=TYLin

(In reply to David Shin[:dshin] from comment #7)

Changes made, try run looks good (Failure cases don't even use table, so it seems unrelated)

Yeah, the R5 run there looks like it's a version of bug 1895092, so it's likely an infra issue and not something you need to worry about. (It matches the "bad" pattern from bug 1895092 comment 16.)

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
Upstream PR merged by moz-wptsync-bot
Flags: qe-verify+

Issue is reproducible on a 2024-05-05 Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 128.0a1 and Firefox 127.0b2 on Windows 10, macOS 12, Ubuntu 22.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: