Automatic update from web-platform-tests Avoid nullptr LayoutInputNode child caused by display-locking. An element may become display-locked while laying out its children. This is bad, but that's an underlying display-locking issue. The recent change crrev.com/c/7957397 added code that assumed that if a BlockNode has children, FirstChild() doesn't return nullptr. But if the node gets display-locked while laying out its own children, FirstChild() will suddenly return nullptr, even if it didn't do so initially. See crbug.com/527144302 for details. Bug: 526163437 Change-Id: Ibb95bb332fa9bd4f424d1b3b1fd226c47dbdc7b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7978977 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1652444} -- wpt-commits: e459ca8f5c8804e243f540c817ed279e8a72c757 wpt-pr: 60898