GCC will pick up whatever `as` is first in PATH when trying to assemble
files. It expects this `as` to have at least as many features as the
`as` detected at configure time when GCC was originally built. We
should ensure that GCC is always picking up an appropriate `as` by
adding its base directory to the search path; otherwise, we get peculiar
assembler errors.
Automatic update from web-platform-testsRevert "Ensure that Config's set of ports is generated atomically. (#11299)" (#11418)
This reverts commit 7018426026884a23def559fc0528fd1f338d4679.
Fixes#11397; per @jdm "my PR didn't help at all" hence reverting
doesn't reintroduce any flakiness.
--
wpt-commits: 97f9d19d172ad73e50446852713e311f57490ec3
wpt-pr: 11418
Automatic update from web-platform-testsMerge pull request #11396 from frivoal/css-ui-2664
[css-ui-4] link cursor over SVG links
--
wpt-commits: 0f651ffe15c8bb81af266d48d2316aeb4dcb8564
wpt-pr: 11396
Automatic update from web-platform-testsCorrectly detect when a multicol descendant becomes or ceases to be a containing block.
When a descendant of a multicol container becomes a containing block for
out-of-flow positioned objects, or ceases to be one, out-of-flow
positioned children may become or cease to be a part of the
fragmentation context.
We didn't detect this correctly. We only checked for transforms (in
addition to position:relative). Make sure we check for filters too, now
that those also establish containing blocks.
Bug: 847328
Change-Id: I7ab47860bb8d9f8d9b0256b25e1123c34f73e8f4
Reviewed-on: https://chromium-review.googlesource.com/1089336
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565210}
--
wpt-commits: bc87c81f9e1cf32934c69921aaa37104a850ed5c
wpt-pr: 11392
Automatic update from web-platform-testsFix the TemporaryFile mode to prevent crashing. (#11382)
Setting the TemporaryFile mode to 'rw+b' in request.py causes an IOError when trying to write to the _buf. Removing the mode, and using the default 'w+b', fixes this issue. Added 2 tests that test for this
--
wpt-commits: 13365c7a94a80b19e0c57b8fc76609e73aea2061
wpt-pr: 11382
Automatic update from web-platform-testsDOM: more window.event tests
To compliment #4790.
--
wpt-commits: 6380b5ce0582cabef270455d698df0830d91ccfc
wpt-pr: 10329
Automatic update from web-platform-testsWorker: Use Document's SettingsObject for top-level module script loading on dedicated workers
This CL makes Document serve its settings object ("outside settings") to
WorkerGlobalScope based on the following HTML spec:
Step 13. "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
This SettingsObject is used as "fetch client settings object" for top-level
module script loading and static imports.
Before this CL, WorkerGlobalScope's settings object ("inside_settings_object")
is used as "fetch client settings object". This is obviously wrong and fails
some web-platform-tests. This change fixes them.
Change-Id: I87a78f38308e262425b848d99dc617dbddeb81e7
Bug: 842553, 845285
Reviewed-on: https://chromium-review.googlesource.com/1084133
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565199}
--
wpt-commits: ed2f4a4d980a609e817b4115d025cd06202a9882
wpt-pr: 11379
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
Nathan Froyd
Olli Pettay
Sebastian Hengst
moz-wptsync-bot
Geoffrey Sneddon
Chris Lilley
Luke Bjerring
Servo WPT Sync
Morten Stenshorne
Matt Falkenhagen
Philip Jägenstedt
David H
Anne van Kesteren
Mike Taylor
Hiroki Nakagawa
Kent Tamura
Wanming Lin
Aleks Totic
Fadi Meawad
Alice Boxhall
Florian Rivoal
Manuel Rego Casasnovas
Josh Matthews
Frédéric Wang
Jake Archibald
Raymond Toy
Simon Pieters