Closed Bug 1541779 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 16221 - [PE] Include visual overflow of self-painting LayoutTableCells for rowspan.

Categories

(Core :: CSS Parsing and Computation, defect, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 16221 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/16221
Details from upstream follow.

Chris Harrelson <chrishtr@chromium.org> wrote:

[PE] Include visual overflow of self-painting LayoutTableCells for rowspan.

If a table cell spans multiple rows, then the row needs to expand its
visual overflow to include the visual overflow of that cell, even if
the cell is self-painting. This is because the table row is the delegated
painter of the background and collapsed borders of such cells.

Bug: 947713

Change-Id: I690991de15ad4c527a8647ab11e5fb302269a2fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548868
Commit-Queue: Chris Harrelson \<chrishtr@chromium.org>
Reviewed-by: Mason Freed \<masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647008}

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Failed to get results from try push
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/5a6d9c07d840 [wpt PR 16221] - [PE] Include visual overflow of self-painting LayoutTableCells for rowspan., a=testonly

https://hg.mozilla.org/mozilla-central/rev/5a6d9c07d840

Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox69: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.