[block-in-inline] Add tests for `getBoundingClientRect`

Bug: 716930
Change-Id: I7a609ae1429bdd4b0361c22cd4daf799257e7ead
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3149307
Commit-Queue: Koji Ishii <kojii@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919919}

[@layer] Use layer order to resolve @counter-style name conflicts

Bug: 1095765
Change-Id: I66c2b64eb885a548f793e9cc7548dca812ab4309
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3151155
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919961}

Parsing for contain-intrinsic-size: auto <length>

Bug: 1199460
Change-Id: I4ec92560c28529269b75c6c41b6e8a28861f6756
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138514
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919900}

webhid: Close service connection when context is lost

This fixes an issue where the execution context could be destroyed
before the mojo connection to the HID service is disconnected, causing
blink::HID to be torn down with pending Promise callbacks.

This CL makes blink::HID an ExecutionContextLifecycleObserver so it
can respond to ContextDestroyed and resolve the pending callbacks.

Bug: 1243284
Change-Id: Ic1860ffa39d7e1fc7197b14c8cb0bbe4570d1115
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3140735
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Matt Reynolds <mattreynolds@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919947}

[css-text] Added 2 hanging-punctuation tests (web-platform-tests#26961)

Added 6 white-space-applies-to-text tests and reference (web-platform…

…-tests#26877)

Revert "[anonymous_iframe] Add WPT for partitioned shared workers"

This reverts commit f028bc8bcc042eb6aceb8209e66eee86248e2b6a.

Reason for revert: failing Mac10.14 Tests crbug.com/1248140

Original change's description:
> [anonymous_iframe] Add WPT for partitioned shared workers
>
> This CL adds a test checking that anonymous iframes get partitioned
> shared workers.
>
> Bug: 1226469
> Change-Id: Ic11085834b567ca178a952828f638b5243eae25d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3148055
> Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
> Reviewed-by: Arthur Hemery <ahemery@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#919676}

Bug: 1248140
Change-Id: Ib66e9199b1a40fd02fbb08bb25f76da71c1f7e25
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3149816
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Gayane Petrosyan <gayane@google.com>
Cr-Commit-Position: refs/heads/main@{#919890}

Fix ref

Revert ScopedForcedUpdate Range changes

This reverts two patches:
http://crrev.com/919277
http://crrev.com/919407
The first patch caused a memory regression, and the second patch is
based on it so it must also be reverted.
The memory regression probably won't be too hard to fix, but since it's
this close to the branch I'm just going to revert them.

Bug: 1236774
Fixed: 1247842
Change-Id: I5c5bb3c3a0a53ba4f6c2ba87a28f0b00fe6e0294
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3152055
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Auto-Submit: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919874}

Improve breaking before nested multicols and their rows.

1. Avoid breaking inside an inner multicol fragment if there were
suboptimal breaks inside even if the inner multicol container didn't
break in the outer fragmentation context. multicol-nested-018.html,
multicol-nested-022.html and multicol-nested-023.html test this.

2. Properly constrain balanced column block-size to remaining space in
the outer fragmentainer.  We used to let unbreakable content override
the remaining space, but this is wrong. This fixes
forced-break-too-short-column.html and
nested-short-first-row-extra-tall-line.html

Store break appeal in NGLayoutResult, rather than in NGBreakToken. The
reason is that we may have a violating break inside a fragment that
happened inside a nested fragmentation context, even if the fragment
doesn't necessarily break within the outer fragmentation context.

Also create a proper break token inside a nested multicol container if
there is none and we want to break before the first piece of column
content. Calling SetDidBreakSelf() manually, like we used to, confused
FinishFragmentation() into thinking that we were past the end of the
block-end content box of the multicol container. This is tested by
nested-with-padding.html Because of this change, the code in
PreviousInnerFragmentainerIndex() needed an update, to ignore this break
token, since break-before tokens don't have a sequence number.

Remove the has_violating_descendant_break flag, and use the break appeal
in the layout result instead. We had a column-balancing bug where where
we were missing break-inside:avoid violations, because such violations
don't affect the child's stored break appeal (the reason for this is
explained in further detail inside CalculateBreakAppealInside()).
Such violations were already propagated correctly to the builder's break
appeal, so now it just works. This is tested by
multicol-fill-balance-014.html . Also remove
LayoutNGBlockFragmentation-specific baselines for
moz-multicol3-column-balancing-break-inside-avoid-1.html because of
this, as we now render identically to the legacy engine.

This change fixes some existing tests. It also made
outer-column-break-after-inner-spanner-2.html render correctly, but not
according to the expectation, which was written for the legacy engine.
The legacy engine fails to push the block with the BR inside entirely to
the next outer fragmentainer. So replce it with a correct test:
multicol-nested-017.html

Bug: 829028
Change-Id: I13b2d95a0eb0407a82c8c24070a6dff4d2f620e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3150413
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#919825}