Closed Bug 1661011 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 25227 - Never re-use the layout result from the fieldset contents wrapper.

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
82 Branch
Tracking Status
firefox82 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Never re-use the layout result from the fieldset contents wrapper.

On the layout object side, all children of a fieldset are wrapped inside
an anonymous fieldset contents block. We'll detect during layout which
of the legend children (if any) will become the rendered legend. Unlike
all other in-flow children of a fieldset element, whose containing block
is the wrapper, the containing block of the rendered legend is the
fieldset layout object itself (not the wrapper child), so if we change /
remove the rendered legend, the wrapper won't be marked for layout.

Bug: 1119400
Change-Id: I5b898af8c7b7e3687def6a2333d43a8ba6af09b1
Reviewed-on: https://chromium-review.googlesource.com/2374526
WPT-Export-Revision: 43a334a098efb5d7ac7018b2f63846d34292c198

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests

Status Summary

Firefox

PASS : 1

Chrome

CRASH: 1

Safari

PASS : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e57b5269bc45 [wpt PR 25227] - Never re-use the layout result from the fieldset contents wrapper., a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in before you can comment on or make changes to this bug.