Bug 1696029 [wpt PR 27866] - [GridNG] Separation of legacy and NG when there is a...

Bug 1696029 [wpt PR 27866] - [GridNG] Separation of legacy and NG when there is a position change, a=testonly

Automatic update from web-platform-tests
[GridNG] Separation of legacy and NG when there is a position change

The logic for invalidating the grid when there is a change in its style
needs to different in legacy and NG. A previous change
https://chromium-review.googlesource.com/c/chromium/src/+/2713389
attempted to change the object that was getting invalidated from the
parent to the containing block. However, this approach will only work
for NG.

Changes in the properties listed in GridStyleChanged already force a
full layout on this box due to how the properties are specified in
third_party/blink/renderer/core/style/computed_style_diff_functions.json5
For out-of-flow elements with grid container as containing block, we
currently need to run the entire algorithm for placing and sizing.

Legacy grid needed the extra invalidation |DirtyGrid()| of the cached
state on LayoutGrid before re-running layout on the grid container.

Bug: 1183122, 1183192
Change-Id: Icc5280e7c25802858b55fc0ace4fc2f16359e09e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2728287
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Commit-Queue: Ana Sollano Kim <ansollan@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#859177}

--

wpt-commits: e5b144368951eb417299e38f4aba2cfd125ef6d5
wpt-pr: 27866