Closed Bug 1828076 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39531 - Don't update view transition style if DisplayLock is locked

Categories

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

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

Don't update view transition style if DisplayLock is locked

There was no check to not update view transition pseudo elements if the
root element was locked for descendant style recalc by
content-visibility. That caused a DCHECK failure that such an element
should never be marked as having descendants that need layout tree
attachment.

Add !ShouldUpdateChildStyle() check to skip view transition style update
in that case.

Bug: 1429947
Change-Id: I89cd0b34deb7c318411382bf52f9300a50f12e2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4422850
Reviewed-by: Vladimir Levin \<vmpstr@chromium.org>
Commit-Queue: Rune Lillesveen \<futhark@chromium.org>
Code-Coverage: Findit \<findit-for-me@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1130325}

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 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/93e861a7b712 [wpt PR 39531] - Don't update view transition style if DisplayLock is locked, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.