Now that source-map-loader uses ChromeLoader, it doesn't need to be loaded
via the Browser Loader. It was mostly used to be able to access window.Worker symbol.
It was also exposing `fetch` global symbol. DevTools Loader wasn't exposing it.
I fixed that as this symbol is available in JSM/ESM.
Differential Revision: https://phabricator.services.mozilla.com/D162966
Automatic update from web-platform-tests
Revert "Drop funcsigs"
This reverts commit ef70ce9623f50e9e7a89bb713920588cfb1259cf.
This broke the WebKit import-w3c-tests script, reverting until someone has time to look more closely into it.
--
wpt-commits: 4a4653e088039aec186d6dc1d488120d77695c3a
wpt-pr: 37442
Automatic update from web-platform-tests
FSA: Allow removing the root of an OPFS
Removes the extra check added in https://crrev.com/c/3123735. See
recent discussion on the spec here:
https://github.com/whatwg/fs/pull/9#discussion_r1042179453
Bug: 1114923, 1399660
Change-Id: I0afd561238ae44dfa055e6fff234e801ee8de616
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4090632
Auto-Submit: Austin Sullivan <asully@chromium.org>
Reviewed-by: Daseul Lee <dslee@chromium.org>
Commit-Queue: Austin Sullivan <asully@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081696}
--
wpt-commits: 1a3f3a52208c41caad21964990f0b08a56d0264c
wpt-pr: 37440
Automatic update from web-platform-tests
[CodeHealth] Update PE attribute tests for a cleaner wpt.fyi status.
- Remove redundant assert messages.
- Combine related asserts into fewer tests.
- Add missing type checks for inherited attributes.
- Clean up the use of action Promises.
Change-Id: I1e87af6e55d13be23a959bd0ee5e28d96a510ab9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4086645
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081495}
--
wpt-commits: 47ce936ed6075bff2bea802ba79b2ec253a90195
wpt-pr: 37386
Automatic update from web-platform-tests
[container-queries] Start CQ search for :host:part() correctly
We are supposed to start the search for container queries at the
ultimate originating element, but we did not respect this for
:host:part() rules. This is because the first iteration of a for-loop
in MatchPseudoPartRules starts with the part_matching_element, which
is used as the starting element for the container queries search.
To meet the "ultimate originating element" criteria, we should instead
start at that element's host.
Fixed: 1399539
Change-Id: Icfc4265f5dae083c15a204f78962e8a356312cdc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4088568
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081384}
--
wpt-commits: 9f571c78869652c5283562c6348a03af9a3fabb6
wpt-pr: 37413
Automatic update from web-platform-tests
[bfcache] Reset NotRestoredReasons for redirect (#37073)
This CL implements resetting of NotRestoredReasons when redirect happens.
For example, a.com->b.com->(back but server redirect)c.com
When this happens, we should not be reporting the reasons for a.com for c.com.
This CL does this by adding NotRestoredReasons as a part of commit navigation params instead of a parameter in CommitNavigation() method.
This is to implement what we discussed here:
https://chromium-review.googlesource.com/c/chromium/src/+/3986625/5..12/content/browser/renderer_host/back_forward_cache_impl.cc#1551
Change-Id: Idee05c88d1073fbe5c3d19c0b9edcd360ce6c1a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4006065
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1080776}
Co-authored-by: Yuzu Saijo <yuzus@chromium.org>
--
wpt-commits: f669a3dcd53b34e995226059b5536de8a4ace04f
wpt-pr: 37073
Automatic update from web-platform-tests
WPT: Allow `window.onload` to contain multiple `test()`s
******************************************************************
*** SHERIFFS: please don't revert this CL if it causes web_tests
to flake/fail. If that happens, the cause is a bad
test. Please mark that test as flaky/fail in
TestExpectations, with a new crbug. Please block the
new bug against crbug.com/1395228. Thanks!
******************************************************************
Prior to this CL, a test like this:
```
<script>
window.onload = () => {
test((t) => { ... }, 'test 1');
test((t) => { ... }, 'test 2');
test((t) => { ... }, 'test 3');
};
</script>
```
would not run anything after test #1. The issue is that the testharness
immediately adds a window load handler that marks `all_loaded = true`,
and that ends the tests as soon as the first result from the first test
is processed. (The test runner waits for the first test because
`Tests.prototype.all_done()` also waits until `this.tests.length > 0`.)
There were various mitigating corner cases, such as if you started
the list of tests with a promise_test(), that would increment a
counter that kept the rest of the tests alive. Etc.
With this CL, the testharness-added window.onload handler runs a
setTimeout(0), so that `all_loaded` is only set to true after all of
the tests are loaded by any window.onload handler.
This exposed a few tests that should have been failing but were
masked by the lack of test coverage - bugs have been filed for
those. Also, several tests that were working around this via various
means are also cleaned up in this CL. I'm sure there are more of
those.
Bug: 1395228,1395226,1307772
Change-Id: I6f12b5922186af4e1e06808ad23b47ceac68559c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4074305
Reviewed-by: Weizhong Xia <weizhong@google.com>
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081558}
--
wpt-commits: e085ff159a16b0a40c38cf745d511c4687bb3937
wpt-pr: 37299
Automatic update from web-platform-tests
Re-implement AVIFImageDecoder::RepetitionCount()
Re-implement AVIFImageDecoder::RepetitionCount() using the new
repetitionCount member of the avifDecoder struct.
Three animated AVIF test files actually contain a repetition count of 0,
so their expected repetition counts in the unit test need to be
adjusted.
The WPT AVIF test file four-colors-flip.avif also contains a repetition
count of 0. Remove all edits from four-colors-flip.avif so that Chrome
will treat a missing repetition count as Infinity for backward
compatibility.
Change-Id: I1963efaf0123fd05f8caabc4cf7d538b058f511f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4053784
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/main@{#1081550}
--
wpt-commits: 88004c48e5f4daff5a98af4d19bb0b7e2198f612
wpt-pr: 37411
Automatic update from web-platform-tests
VT: Ensure all layers that recalculate their draw props push props too
This patch is a more comprehensive fix for the referenced bug.
Previously, we've only addressed opacity animations, but the same bug
is present for transform animations as well. The problem with
transforms is that to detect changes in the matrix, we need to do
a lot of float comparisons. It seems better to just unconditionally
say that if we recalculated draw properties, then that layer needs
to push properties as well.
Note for picture layer impls, this is still a no-op, since they
always push their properties.
R=pdr@chromium.org
Bug: 1385432
Change-Id: I6df15e6e344507f26336698e4bf890728690da52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4081632
Reviewed-by: Philip Rogers <pdr@chromium.org>
Auto-Submit: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081505}
--
wpt-commits: 74b130a8568849fbe41898789c19c1382171e931
wpt-pr: 37355
Automatic update from web-platform-tests
Rework load/error event dispatch for <use> elements
The way events are dispatch (for <use> 'load' of external resources) is
racy, since the resource reference can change from "external" to "local"
in the space between the resource finished loading and the event was
dispatched.
Instead post 'load' (and 'error') events as cancellable tasks, and then
cancel the event task if the target reference changes before the event
has been dispatched. This somewhat matches similar types of loading
sequences.
Fixed: 1130925
Change-Id: Icd4e89a0288ab0ed5e4c7ee0fe218ee30329d477
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4047289
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081477}
--
wpt-commits: 6f1c494b9a42cfe0703bcfa84d07ccdba82b7152
wpt-pr: 37353
Automatic update from web-platform-tests
Revert "Prerender2 CSP: Implement script-src 'inline-speculation-rules'"
This reverts commit 9a89f759b68a49bb969ec1a7a4d3d966cb5707bc.
Reason for revert: Introduces consistent web tests failures on multiple Mac bots.
https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/11486/overviewhttps://ci.chromium.org/ui/p/chromium/builders/ci/mac12-arm64-rel-tests/4418/overviewhttps://ci.chromium.org/ui/p/chromium/builders/ci/Mac12%20Tests/4679/overview
Original change's description:
> Prerender2 CSP: Implement script-src 'inline-speculation-rules'
>
> This patch implements CSP 'inline-speculation-rules' source for
> <script type="speculationrules">. This source is available only for
> script-src directive, and can permit inline script tags that has
> the type attribute with "speculation-rules". This allows developers
> to permit inline script only for speculationrules.
>
> With this patch, the change is applied only for isolated worlds
> where we run Chrome Extensions. But it will be extended to the
> open web platform once we publish a patch spec and follow the I2S.
>
> Bug: 1382361
> Change-Id: I69b1f3e61e64c3f956964fe59e2e847239654c81
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4056835
> Reviewed-by: Dominic Farolino <dom@chromium.org>
> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
> Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> Reviewed-by: Mike West <mkwst@chromium.org>
> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1081341}
Bug: 1382361
Change-Id: Id9507ac4fe114b3f2b61a43df592f0efaf358e87
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4092170
Reviewed-by: Monica Basta <msalama@chromium.org>
Commit-Queue: Monica Basta <msalama@chromium.org>
Owners-Override: Monica Basta <msalama@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1081474}
--
wpt-commits: c786cc8cec396f7a793d2cd0e6a517aa993bfb96
wpt-pr: 37430
Automatic update from web-platform-tests
[scroll-animations] Support animation-duration:auto
This CL supports using 'auto' (explicitly) as an animation duration.
Whether or not 'auto' should become the new initial value of
animation-duration will be handled separately.
Fixed: 1382873
Change-Id: I50a669fdf53323f32299948081d316997c7820c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4079648
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081438}
--
wpt-commits: f12151ee06f095fc75a42bef5613e5f3d8220431
wpt-pr: 37359
Automatic update from web-platform-tests
WPT for testing content-type parsing
Browsers may not parse out Content-type headers and mime-type strings correctly. This WPT makes use of the field contentType in PerformanceResourceTiming to validate the parsing that was done.
Bug: 1366706
Change-Id: I87a443f6f8890d5f43147ec96d8c3c70c0185de3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4058549
Commit-Queue: Abin Paul <abin.paul1@gmail.com>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081390}
--
wpt-commits: 77eadc1dc505a2d27794c06aa7fdb2d8fefb4df9
wpt-pr: 37175
Automatic update from web-platform-tests
Prerender2 CSP: Implement script-src 'inline-speculation-rules'
This patch implements CSP 'inline-speculation-rules' source for
<script type="speculationrules">. This source is available only for
script-src directive, and can permit inline script tags that has
the type attribute with "speculation-rules". This allows developers
to permit inline script only for speculationrules.
With this patch, the change is applied only for isolated worlds
where we run Chrome Extensions. But it will be extended to the
open web platform once we publish a patch spec and follow the I2S.
Bug: 1382361
Change-Id: I69b1f3e61e64c3f956964fe59e2e847239654c81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4056835
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081341}
--
wpt-commits: 6699aa7554add6df9c9fc23de808772a19dcfa34
wpt-pr: 37327
Automatic update from web-platform-tests
Revert "Use direct compositing for canvases rendered on the CPU"
This reverts commit c6b115aecd3b02b953bcdbffd5884910c25a6a69.
Reason for revert: fast/canvas/canvas-incremental-repaint.html is failing on Mac12 Tests
https://ci.chromium.org/ui/p/chromium/builders/ci/Mac12%20Tests/4657/overview
Original change's description:
> Use direct compositing for canvases rendered on the CPU
>
> Before this CL, we already had the plumbing for presenting CPU-rendered canvases via GpuMemoryBuffer for direct compositing. That code path was originally implemented to support LowLatency mode. With this change, we exercise the GpuMemoryBuffer code path for "regular" latency canvases. This accelerates compositing, especially for pages that have many canvases.
>
> With this change, MotionMark Images test runs significantly faster, especially with angle/metal enabled.
>
> Bug:1363627
>
> Change-Id: I25b9e3105773fee84a1fc88432ed6640dac4c976
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4081383
> Commit-Queue: Justin Novosad <junov@chromium.org>
> Reviewed-by: Juanmi Huertas <juanmihd@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1080998}
Bug: 1363627
Change-Id: Idb59c9044dcc584db332a18a28312e1f4332d14e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4090966
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Keishi Hattori <keishi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081287}
--
wpt-commits: ec7818ad7daec0b07b3815cb7c5f02498dab0a0d
wpt-pr: 37416
Automatic update from web-platform-tests
Fix a bug in CSSNumericValue parsing
In CSSNumericValue parsing, there's a part of code that tries to merge
consecutive binary operations (e.g., `a + b + c`) into a variable
Typed OM operation node. The code was written before the introduction
of min/max/clamp, and incorrectly loops into such nodes, and then tries
to convert a min/max/clamp as a binary arithmetic operation.
This patch makes it aware that there are comparison nodes in the
expression tree and therefore fixes the bug.
Fixed: 1395232
Change-Id: Iff12c5f26785effa716b705630c21219935f9861
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4090552
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081264}
--
wpt-commits: f8579f36b038208e5a7feef1ff1658871643c508
wpt-pr: 37414
Automatic update from web-platform-tests
Only synthesize a 'viewBox' in <img> for the document element <svg>
SVGSVGElement::ShouldSynthesizeViewBox() needs to check that it is the
document element as well.
Use the IsDocumentElement() helper from Element, and replace another
instance of the same check as well.
Fixed: 1313530
Change-Id: I785a8ce83780cc2a4c9d697065453f69bc3d69e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4079162
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081216}
--
wpt-commits: 161ce8659673b5d66b1bb35e7ea96700f10b3d30
wpt-pr: 37356
Automatic update from web-platform-tests
Invalidate ancestor-chain in FilterPrimitiveChanged()
Since a descendant of a resource - for example a <mask> - can reference
a <filter> we need to walk up the ancestor chain to look for resources.
Factor out parts of LayoutSVGResourceContainer's
MarkForLayoutAndParentResourceInvalidation() into separate helpers
(InvalidateAncestorChainResources() and InvalidateDependentElements())
so that they can be called from the FilterPrimitiveChanged() handler.
Fixed: 1297837
Change-Id: I203b2087a441c1cb564f6f44e58e93c38237af1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4085050
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081214}
--
wpt-commits: 68dd1e3b016a4e6385f725219b944ec5747696a2
wpt-pr: 37383
