Bug 1726613 [wpt PR 30091] - content-visibility: Ensure that fragment nav doesn't...

Bug 1726613 [wpt PR 30091] - content-visibility: Ensure that fragment nav doesn't happen for hidden elements., a=testonly

Automatic update from web-platform-tests
content-visibility: Ensure that fragment nav doesn't happen for hidden elements.

Currently fragment navigation depends on whether the element has a
layout object, so by default it wouldn't work on content-visibility:hidden
subtrees _unless_ the property was added after a layout object was
created, then it would scroll.

That's inconsistent and we should just not scroll in any case. That's
similar to what display:none would do here, since there would be no
layout object. Note that this only applies to hidden, and not auto. With
auto, or any "activatable" case, we would first create a layout object
by updating the layout tree outside of this code, and then scroll.

R=chrishtr@chromium.org, futhark@chromium.org
Bug: 1241496

Change-Id: Iaeb65a1e2ad512868b4372ee658bf7f0f1f343ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3107507
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#913821}

--

wpt-commits: a891d839001f353cb2f206fbcd7f8395183c118d
wpt-pr: 30091