Fix netinfo Web Platform Test

self.isWorker was always failing which caused the test to fail. Align
the isWorker call with other idlharness.any.js

Change-Id: If8f909147c0333905814c758734c699c8bbb0e1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551464
Reviewed-by: Tarun Bansal <[email protected]>
Commit-Queue: Dave Tapuska <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647505}

[UserTiming] Move UserTiming L3 tests to WPT

In preparation for shipping, move tests to WPT. Remove the Virtual Test
Suite.

Bug: 758385
Change-Id: Idc864521d35fce9e4ee4c44f2b3d32130fc88053
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550692
Commit-Queue: Nicolás Peña Moreno <[email protected]>
Reviewed-by: Liquan (Max) Gu <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647406}

Use pre-resolved resource in SVGPatternElement::ReferencedElement

SVGPatternElement::BuildPendingResource() resolves a resource reference
for 'href' on the <pattern> element using the TreeScope-based "resource
store". SVGPatternElement::ReferencedElement() (re-)resolves the same
reference on its own. Because of this inconsistency we could end up
having a reference to a LayoutObject in the associated SVGResources
object, but not have hooked up a client reference for the (originating)
<pattern> element.

Use the SVGResource to resolve the target element in ReferencedElement()
too so that there's only one source of truth.

Bug: 949015
Change-Id: I001c4f9260bdc4599843cd53833b749fd320daa5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550426
Reviewed-by: Stephen Chenney <[email protected]>
Commit-Queue: Fredrik Söderquist <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647295}

fix intermittent in Event-dispatch-on-disabled-elements.html

change how transitions are triggered and extend the animation/transition time.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1531567
gecko-commit: 1d56a0d3a3236253b297d9928083175c2d1b403e
gecko-integration-branch: central
gecko-reviewers: birtles

Update target_blank_implicit_noopener(_base) tests to have long timeout

These two tests seem to hit timeouts on debug builds.

Bug: 930873
Change-Id: I0b383e6454f29cd40f82c3553f2cbff5efa4769c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550282
Commit-Queue: Takashi Toyoshima <[email protected]>
Commit-Queue: Kunihiko Sakamoto <[email protected]>
Auto-Submit: Takashi Toyoshima <[email protected]>
Reviewed-by: Kunihiko Sakamoto <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647212}

service worker: Support DataPipeGetters in navigation request body.

This removes a DCHECK that there are no DataPipeGetters in the body. It
was originally added because I thought it wasn't possible and didn't
want to manually clone the body to handle that case. But it is possible,
and it's no longer necessary to manually clone after r543639
<https://chromium-review.googlesource.com/c/chromium/src/+/963085/>
anyway.

This adds a test that would fail before this CL.

Bug: 944145
Change-Id: Ia7ceba438e741150508cac5fa3d6c56c08137642
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548883
Reviewed-by: Kenichi Ishibashi <[email protected]>
Commit-Queue: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647528}

[css-variables] Limit length of substituted token sequence.

A recent amendment to the spec requires us to impose a limit (without
specifying what that limit is).

Mozilla has already implemented a limit. (A maximum string representation
of 1MB, I believe). Unfortunately, we can't implement the limit the same
way, as we don't have a quick way of knowing what the string representation
of a given variable is; we would have to serialize the tokens. (This may
change in the future, though).

This CL suggest a limit of 16K tokens instead, without imposing any direct
limit on the string backing of those tokens. That means that there is
effectively no limit on e.g. data URLs.

The problem of a large initial string duplicated many times with the
billion laughs technique is mitigated by the fact that String is reference
counted: we do end up with a large amount of String instances, but they
all point to a fairly limited number of StringImpls. I have added a unit
test to verify this behavior.

Also updated the test: --v31 wasn't declared, and 'content' does not
accept multiple strings separated by commas.

BUG=939289
[email protected], [email protected]

Change-Id: I6d4cb5fed4d752ff409db390fd09f8f91ea54bcb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549058
Commit-Queue: Anders Hartvoll Ruud <[email protected]>
Reviewed-by: Emilio Cobos Álvarez <[email protected]>
Reviewed-by: Rune Lillesveen <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647220}

[service-workers] Improve test stability (web-platform-tests#16235)

The `fetch_tests_from_worker` utility function initiates an asynchronous
operation. The requests tests are eventually defined, but if the harness
status has detected completion before this, the new tests will trigger
undefined behavior.

In order to avoid this race condition, ensure that the test which is
active at the call site does not complete until after the new tests have
been fetched.

Updating Edge os_version os_build powershell strings to be raw_strings.

CORB shouldn't block application/dash+xml videos.

Bug: 947498
Change-Id: I4925f5209e507f8e39ea324de3a9c6f48e1747f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546671
Reviewed-by: Charlie Reis <[email protected]>
Commit-Queue: Łukasz Anforowicz <[email protected]>
Cr-Commit-Position: refs/heads/master@{#647089}