Morten Stenshorne
ab48b2b91e
Automatic update from web-platform-tests Always check for spanner prevention on style change. We relied on needing full layout for this check to be run, but it's possible for non-layout-affecting property changes to affect whether spanners are allowed or not. In particular, transforms prevent spanner descendants, but removing or adding a transform doesn't affect layout, unless doing so also changes whether a stacking context should be established or not. Also, we need to run this not only when spanners become valid, but also when they become invalid (e.g. when adding a transform to an element that previously didn't prevent spanner descendants). Bug: 500832364 Change-Id: Icbf746cc3d6045901517e5ab2425659632192061 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7743004 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#1612519} -- wpt-commits: 1ed1c24c728634aee3e2afb1094b69d49df8506a wpt-pr: 59072
18 lines
771 B
HTML
18 lines
771 B
HTML
<!DOCTYPE html>
|
|
<title>Remove transform but keep stacking context root, descendant spanner candidate</title>
|
|
<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
|
|
<link rel="help" href="https://issues.chromium.org/issues/500832364">
|
|
<link rel="match" href="../reference/ref-filled-green-100px-square.xht">
|
|
<p>Test passes if there is a filled green square and <strong>no red</strong>.</p>
|
|
<div style="width:100px; height:100px; background:red;">
|
|
<div style="columns:2;">
|
|
<div id="ancestor" style="transform:rotate(5deg); position:relative; z-index:1;">
|
|
<div style="column-span:all; height:100px; background:green;"></div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<script>
|
|
document.body.offsetTop;
|
|
ancestor.style.transform = "none";
|
|
</script>
|