Bug 1727647 [wpt PR 30186] - Invalidate for changed PaintedOutputInvisible when a...
commit15086c7946d5bc82eb254597c07ab1768da9a72c
authorXianzhu Wang <wangxianzhu@chromium.org>
Wed, 1 Sep 2021 14:09:20 +0000 (1 14:09 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Thu, 2 Sep 2021 10:30:37 +0000 (2 10:30 +0000)
treed04a40901b8e24dcd46177f1db8675a58ed0d03d
parentdfd723c533259f74c0def1ed25ac8c66afb85f2f
Bug 1727647 [wpt PR 30186] - Invalidate for changed PaintedOutputInvisible when a PaintLayer is removed, a=testonly

Automatic update from web-platform-tests
Invalidate for changed PaintedOutputInvisible when a PaintLayer is removed

When opacity on an element changes from 0 to 1, the PaintLayer may be
removed. We should do the same as PaintLayer::StyleDidChange() for
change of PaintedOutputInvisible to invalidate the subtree.

Bug: 1242746
Change-Id: I6d5b7831e6a21f12c6139da24b9c3078b68f52aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3119761
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#915417}

--

wpt-commits: 77a3d15bfb22b2f654bceaec223311a8c3d05e7f
wpt-pr: 30186
testing/web-platform/tests/css/css-color/body-opacity-0-to-1-stacking-context.html [new file with mode: 0644]