Automatic update from web-platform-testsCreate permissions test suite with IDL tests (#9301)
--
wpt-commits: 5133c54714fe33a25e7182ba04cb73156ca4abdb
wpt-pr: 9301
Automatic update from web-platform-tests[PageLifecycle] Fix WPT test by hiding the page before freezing
Freezing can only work on hidden pages, currently there is no easy way
in webdriver that allows us to hide the page.
A new webdriver API is in the works to enable that, but meanwhile, for
all testing API, we have to couple hiding with freezing.
This CL does that and reenables the test with Network Service.
Bug: 837709, 848604
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ib5c513aefb219cef38a563be81fe8abf4b354051
Reviewed-on: https://chromium-review.googlesource.com/1089354
Commit-Queue: Fadi Meawad <fmeawad@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565031}
--
wpt-commits: 8121170bf45471a35105d12f6bf8a070216d1db6
wpt-pr: 11390
Automatic update from web-platform-testsPass useChardet=False for HTML files in SourceFile
When chardet is installed, this makes the no-manifest case 7% faster.
--
Try the built-in XMLParser and then fallback to ours
While this means in the worst-case we parse almost the entire file
twice (when there's an entity at the end), the more common case is an
unsupported encoding (which, of course, is at the start), and the most
common case is never falling back. In the no-manifest case, this is
22% faster.
--
wpt-commits: 31a95315daf06dcaff2034692358e76662c2cdc7, b7cc2f1eb7b29fa75a3e0baaf672a9d03372d17a
wpt-pr: 11385
Automatic update from web-platform-testsMerge pull request #11365 from frivoal/git-doc-serve
Mention the need to setup the web server in the github tutorial
--
wpt-commits: c7c54d3d4b15377d05cf7650e156b9c7e0ce103d
wpt-pr: 11365
Automatic update from web-platform-testsMerge pull request #11366 from frivoal/css-text-2682
[css-text-3] Add test for intrinsic sizing and overflow-wrap
--
wpt-commits: e89577697adb828fcdad54d27a15524dd125149d
wpt-pr: 11366
Automatic update from web-platform-tests[css-contain] Layout containment overflowing contents as ink overflow
Text form the spec
(https://drafts.csswg.org/css-contain/#containment-layout):
"If the contents of the element overflow the element,
they must be treated as ink overflow."
The patch modifies LayoutBox::LayoutOverflowRectForPropagation()
so the overflowing contents of an element with "contain: layout"
are treated as ink overflow. That way they don't interfere at all
in the layout of its ancestors.
BUG=843320
TEST=external/wpt/css/css-contain/contain-layout-015.html
Change-Id: Iedd47edf46a0e4ce0e4102abe5881d25771fe0fa
Reviewed-on: https://chromium-review.googlesource.com/1087462
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#564826}
--
wpt-commits: 892738fabee6bc4c7e720177f45e295fcb981b8d
wpt-pr: 11374
Automatic update from web-platform-testsWorker: Add referrer tests for ES Modules on dedicated workers
Referrer handling spans multiple algorithms in multiple specs, so I leave only
the entry points of them.
For top-level module script loading and static imports, referrer is determined
based on the "outside settings":
"Fetch a module worker script graph given url, outside settings, destination,
the value of the credentials member of options, and inside settings."
https://html.spec.whatwg.org/multipage/workers.html#worker-processing-model
For dynamic imports, referrer is determined based on the "referencing script's
settings object". In this case, it's "inside settings":
Step 2.4: "Fetch a module script graph given url, referencing script's settings object,
"script", and options. Wait until the algorithm asynchronously completes with
result."
https://html.spec.whatwg.org/multipage/webappapis.html#hostimportmoduledynamically(referencingscriptormodule,-specifier,-promisecapability)
These tests are still failing. Subsequent CLs will fix them.
Bug: 842553
Change-Id: I3855b91c7e6ba93f5c99fb63b24b6274e6b43211
Reviewed-on: https://chromium-review.googlesource.com/1088339
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564811}
--
wpt-commits: 4b4c626fc8602d1d06680a7d298789708fae5cd3
wpt-pr: 11369
Automatic update from web-platform-testsEnsure that Config's set of ports is generated atomically. (#11299)
--
wpt-commits: 7018426026884a23def559fc0528fd1f338d4679
wpt-pr: 11299
Automatic update from web-platform-testsMake fetch-event.https.html faster.
It was registering a service worker for each test case, and had a lot
of test cases.
This changes the file to register a single service worker at the
beginning, and unregister it at the end.
Bug: 847787
Change-Id: Ic2536824a3c57e86bb5e042287e9e62e6222ad9a
Reviewed-on: https://chromium-review.googlesource.com/1087188
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564770}
--
wpt-commits: d3f16722cc61d5e606e82f84c03e6c344d70b4ba
wpt-pr: 11358
Automatic update from web-platform-testsFetch: test identity encoding for range requests
For https://github.com/whatwg/fetch/pull/751.
--
wpt-commits: 1421a4a976d4d8263bde4864a1ce412eba106d39
wpt-pr: 11291
Automatic update from web-platform-tests[css-contain] Disable layout containment for certain elements
Text from the spec
(https://drafts.csswg.org/css-contain/#containment-layout):
"... if the element is an internal table element other than
display: table-cell, or if the element is an internal ruby element,
or if the element’s principal box is a non-atomic inline-level box,
layout containment has no effect."
The patch disables "contain: layout" for internal table elements
but table cells, internal ruby elements and
non-atomic inline-level boxes.
Some of the new tests pass or fail incidentally due to crbug.com/785212,
once that's fixed all the tests should be working as expected.
BUG=843329
TEST=external/wpt/css/css-contain/contain-layout-008.html
TEST=external/wpt/css/css-contain/contain-layout-009.html
TEST=external/wpt/css/css-contain/contain-layout-010.html
TEST=external/wpt/css/css-contain/contain-layout-011.html
TEST=external/wpt/css/css-contain/contain-layout-012.html
TEST=external/wpt/css/css-contain/contain-layout-013.html
TEST=external/wpt/css/css-contain/contain-layout-014.html
Change-Id: I5f0893a9ce69dc8e76cf16acb1b8556bf0e02adf
Reviewed-on: https://chromium-review.googlesource.com/1087268
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#564631}
--
wpt-commits: c0fbd59769588391d78838086bd02ad394301655
wpt-pr: 11359
Automatic update from web-platform-testsReland "WaveShaper must output non-zero values even if input is silent"
This is a reland of 325b492fe733ba4c8b2128069a0a232fea1789e3
Initialize tail_time_ in constructor so we don't have uninitialized
variable.
Original change's description:
> WaveShaper must output non-zero values even if input is silent
>
> If the curve for the WaveShaperNode is such that a zero input produces
> a non-zero output, the WaveShaperNode needs to output that value even
> if the input is silent (or disconnected).
>
> Do this by setting the tail time of the processor to 0 or infinity
> depending on whether the curve specifies an output value of zero or
> not, respectively.
>
> Bug: 807301
> Test: WaveShaper/silent-inputs.html
> Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b
> Reviewed-on: https://chromium-review.googlesource.com/896266
> Commit-Queue: Raymond Toy <rtoy@chromium.org>
> Reviewed-by: Hongchan Choi <hongchan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564186}
Bug: 807301
Change-Id: I866c5b303b40c1245d86daf43c592eed39d6a9c9
Reviewed-on: https://chromium-review.googlesource.com/1087427
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564630}
--
wpt-commits: 57285cd910b61105ec3b6b8a49d8e875ff8dec69
wpt-pr: 11360
Automatic update from web-platform-tests[LayoutNG] Fix flex BODY in quirks mode
We were not updating margins correctly inside NGBlockNode::RunOldLayout.
Symptom was that BODY(flex) block size was too big when HTML had margins
inside quirks mode.
Another side effect of this fix is two crashes have gone away.
Added explicit test case for BODY(flex) in quirks mode.
Bug: 849490
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Id0ce0910144c81fc254646110424f36c898f9ebd
Reviewed-on: https://chromium-review.googlesource.com/1086381
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564629}
--
wpt-commits: 8bafc093504c38befdb4e63d9d1d1dcee9bf81e4
wpt-pr: 11337
Automatic update from web-platform-testsFix bugs in split-up encoding tests
Bugs were introduced in d6c29bef8d4bcdfe4f689defca73360b07647d71
* Some script paths were wrong
* A big5 test referenced eucjpEncoder instead of big5Encoder
* That big5 test also referenced encode-form-common.js instead of
encode-href-common.js
Fixes#11015.
Also add code to generate variants.
--
wpt-commits: 5e0fea392c570e81ec7932466ac4c142ff83606d
wpt-pr: 11292
Automatic update from web-platform-testsMerge pull request #11313 from web-platform-tests/woff2-sync-up
Sync up tests against https://github.com/w3c/woff2-tests
--
wpt-commits: 40ff5f965fd8dfaaf426d2037632bb997fc91c3d
wpt-pr: 11313
Automatic update from web-platform-testsMerge pull request #11324 from Loirooriol/css-logical-longhands
Add test for logical box model longhand properties
--
wpt-commits: 096cc8f668deca283a93e19b73dcf21fd8cf75b8
wpt-pr: 11324
Automatic update from web-platform-testsAdd tests that deal with applying number format specifiers on Symbols
--
wpt-commits: a21cb02941464102abb91349b732f0864a2d2586
wpt-pr: 9488
Automatic update from web-platform-testsMake check_stability.py use the --verify code
Note this doesn't yet address #9874, as it currently only runs the
repeat_restart mode of --verify (as it did previously).
--
Fix#10921: make --stability use the same code as --verify
--
Make --verify-log-full not override log level
--
wpt-commits: 38809cb9636e65d9083453c2400024f567c7f687, 5bd42c170ce485e9f26eeac3a1f0b919d0fa3106, d564a348a73af817ff565814ebf522ca5991aa55
wpt-pr: 10988
Automatic update from web-platform-testsMake IndexedDB/support.js work in workers
This should fix the test
html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/serialization-via-idb.any.worker.html
Part of #11269.
--
wpt-commits: 60a937de7bd20eb1890893a48423a79b096866d8
wpt-pr: 11348
Automatic update from web-platform-testsRedirect POST requests using .py resource
Part of #11269.
Also see #11343.
--
wpt-commits: ec9ffb132d24fa16088b90db12a65509b72ef826
wpt-pr: 11354
Automatic update from web-platform-testsTest for used column-count when column-count/width are not auto (#10250)
--
wpt-commits: 8b089cb6cebe9c83a471e5cfb10a1570dad65ed4
wpt-pr: 10250
Automatic update from web-platform-testsXMLHttpRequest: upload listener flag
Tests for https://github.com/whatwg/xhr/issues/95.
--
wpt-commits: 1706eb31b901d4e5ce8bb873ffb5b31bb01e1e58
wpt-pr: 5122
Automatic update from web-platform-tests[LayoutNG] Need to know when establishing a new FC during min/max calculation.
When we have to lay out an object to determine its min/max inline size,
and the node establishes a new formatting context, we need to create a
constraint space that reflects this. The block size of the float needs
to be included in the block size of its container, because this block
size will be the min/max preferred inline size of the container of that
container, if the writing modes are orthogonal.
Avoid some duplicate code for creating the constraint space builder. The
second builder, the one that redoes layout with infinite available space
now gets SetFloatsBfcOffset() called, which was previously missing, but
that must have been an oversight.
This fixes the recently introduced regression with
fast/multicol/vertical-rl/column-rules.html and also another test.
Wrote a new test that tests exactly what I wanted to fix as well.
Bug: 847807
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I7b28a0ef8061fc3089deb488ad0a78b81776295d
Reviewed-on: https://chromium-review.googlesource.com/1084989
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564438}
--
wpt-commits: aa5ec97282685cba4a2ae34165ddb5043c251e39
wpt-pr: 11330
Automatic update from web-platform-testsHTML: Fix sandbox-disallow-same-origin.html to expect SecurityError
Part of #11269.
--
wpt-commits: e4fd758fb3ed204ec4234eb678323273a99eb685
wpt-pr: 11341
Automatic update from web-platform-testsExperimental Priority Hints support on fetch() API
Adding support for Priority Hints on the fetch() API under an
experimental flag. This adds the notion of importance to core/fetch
code, and adds a new member to the RequestInit dictionary to communicate
developer-specified "importance" downstream.
R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws
Bug: 821464
Change-Id: Ib96a128d77004029e86122c07552250c697dea5f
Reviewed-on: https://chromium-review.googlesource.com/1084063
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#564410}
--
wpt-commits: dae7535c0428fbf057a5c39f324d5a3f47ba64c7
wpt-pr: 11317
Automatic update from web-platform-tests[wptrunner] End Sauce Connect process gracefully (#11334)
Previously, the Sauce Connect process was closed gracefully in response
to prolonged period of inactivity. This procedure was not used under
normal operating conditions.
Factor graceful shutdown logic into a new method, `quit`, and reuse this
method to end the process following successful test completion.
--
wpt-commits: 2bd11b91d490ddd5237bcb6d8149a7f25faaa101
wpt-pr: 11334
Automatic update from web-platform-testsRevert "WaveShaper must output non-zero values even if input is silent"
This reverts commit 325b492fe733ba4c8b2128069a0a232fea1789e3.
Reason for revert: Broke webaudio/.../waveshaper-364379.html in
webkit_layout_tests. See https://crbug.com/849535
Original change's description:
> WaveShaper must output non-zero values even if input is silent
>
> If the curve for the WaveShaperNode is such that a zero input produces
> a non-zero output, the WaveShaperNode needs to output that value even
> if the input is silent (or disconnected).
>
> Do this by setting the tail time of the processor to 0 or infinity
> depending on whether the curve specifies an output value of zero or
> not, respectively.
>
> Bug: 807301
> Test: WaveShaper/silent-inputs.html
> Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b
> Reviewed-on: https://chromium-review.googlesource.com/896266
> Commit-Queue: Raymond Toy <rtoy@chromium.org>
> Reviewed-by: Hongchan Choi <hongchan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564186}
TBR=rtoy@chromium.org,hongchan@chromium.org
Change-Id: I29fd96b1a9dd2b87db12867031399b069beba706
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 807301, 849535
Reviewed-on: https://chromium-review.googlesource.com/1086647
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564359}
--
wpt-commits: fa5ee47808411c866d09ad6a34dccf383b097bca
wpt-pr: 11338
Automatic update from web-platform-testscustom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded
createElement('my-element', undefined) was not being upgraded, though both
createElement('my-element') and createElement('my-element', {}) were.
Bug: 841725
Change-Id: Id43b21f8e1cad10745dedf3699691da7ad85cf03
Reviewed-on: https://chromium-review.googlesource.com/1084007
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564352}
--
wpt-commits: 8a5301b16f5e913bf9ffbb7d76abfda9d2435af2
wpt-pr: 11312
