Remove erroneous assertions from field-sizing-input-number.html (#51221)

It's wrong to assert that a field-sizing content number input should be the same height as a fixed one.

add missing inputs to urlpatterntestdata.json (#51220)

webrtc wpt: assert that a remote prflx usernameFragment is not expose…

…d in getStats when not known via signaling

WPT for
  https://webrtc-review.googlesource.com/c/src/+/366562

BUG=webrtc:375571816

Change-Id: I3f61f43fc88633f8c584535f280c06122cff1742
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6330947
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1429895}

[EditContext] Deactivate EditContext earlier to prevent being impacte…

…d by DispatchFocusEvent

EditContext's activation is synced with the associated element being
focused or not. If an element loses focus, its associated EditContext
is deactivated.
Before this patch, deactivate the EditContext associated with
`old_focused_element` after `DispatchFocusEvent`. However,
`DispatchFocusEvent` could potentially result in another change in
focus, which would prevent the EditContext's from being deactivated.

Bug: 375711382
Change-Id: I4fb422602faeae5145b3431aee063d367b69fbd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6332446
Reviewed-by: Dan Clark <daniec@microsoft.com>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Peng Zhou <zhoupeng.1996@bytedance.com>
Cr-Commit-Position: refs/heads/main@{#1429887}

Clean up leftover getInnerHTML() stuff

The [1] CL removed this feature, but apparently left a few things
in the codebase. This CL attempts to finish the job.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/6028938

Bug: 41492947
Change-Id: Iea7a95787f8ea22b5f300561434701bd9162472d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6319002
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Traian Captan <tcaptan@chromium.org>
Commit-Queue: Traian Captan <tcaptan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1429841}

Make interesttarget buttons non-user-selectable

This is required, in order to be able to long-press a button
like this on mobile platforms. Without this change, the long
press highlights the word within the button that was long-
pressed, which is an odd experience.

See whatwg/html#8228 for a very
related discussion about *all* buttons. Due to the fact that
the current behavior is quite odd on mobile, I am more
inclined to think we should just ship that behavior across
all buttons. But for now, this just modifies interesttarget.

Bug: 40860451,326681249
Change-Id: Ieb77f44ae59e63fcfbbf7c78808169b45a4ba3ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6319439
Reviewed-by: Di Zhang <dizhangg@chromium.org>
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1429832}

[reading-flow] Implement source-order keyword

Per CSSWG resolution [1]:

- RESOLVED: Resolution to restore previous reading order property and
use it as a starting point for reading order flow.
- RESOLVED: as a starting point, define that if the reading order of 2
items is equivalent, reading flow breaks the tie.

We add the new keyword source-order as a valid keyword for the
reading-flow property. When set on a flex, grid or block layout
box, it is recognized as a reading flow container that should follow
DOM tree order, but that order can be overwritten by reading-order.

We remove the sorting by reading-order in flex/grid algorithms added at:
https://chromium-review.googlesource.com/c/chromium/src/+/6244985

Instead, this sorting happens inside the focus controller logic, once
a list of reading flow elements are defined.

Accessibility tree is not handled yet and will be updated in a separate
patch.

[1] w3c/csswg-drafts#11208 (comment)

Change-Id: I0859f7675651b57bc1329bef8a23e49ed7906436
Bug: 393550130
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6333684
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1429811}

Test documents loaded from local schemes inherit TT CSP rules.

See https://w3c.github.io/webappsec-csp/#security-inherit-csp

Differential Revision: https://phabricator.services.mozilla.com/D239878

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1952498
gecko-commit: 47c6b68961657a9091a30a84259e34a8056d46f7
gecko-reviewers: smaug

nsFind: Return null if boundary points are removed from the DOM tree.

Differential Revision: https://phabricator.services.mozilla.com/D240494

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1949877
gecko-commit: c51bc6c076a9d418078ab86c919f56420a30d339
gecko-reviewers: emilio

Remove erroneous assertions from field-sizing-input-number.html (#51221)

It's wrong to assert that a field-sizing content number input should be the same height as a fixed one.