Automatic update from web-platform-testsPreparation of moving LayoutTests to web_tests.
* layout_test_content_browser_client.cc:
Pass --tests-in-blink flag to a renderer process.
GetWebTestsFilePath() in blink_test_helpers.cc needs this flag.
* LayoutTests/editing/assert_selection.html
* LayoutTests/editing/assert_selection.js
* LayoutTests/editing/execCommand/insert-paragraph-into-table-expected.txt
Drop 'LayoutTests/' part from error description
* LayoutTests/external/wpt/bluetooth/resources/bluetooth-helpers.js
* LayoutTests/external/wpt/webusb/resources/usb-helpers.js
Support web_tests/ as well as LayoutTests/
* LayoutTests/fast/js/exception-line-number-expected.txt
* LayoutTests/fast/js/script-tests/exception-line-number.js
Drop 'LayoutTests/' part from error description
Bug: 843412
Change-Id: I817b40bb2e7edf0216a32d9f3a3e2320e4b6956a
Reviewed-on: https://chromium-review.googlesource.com/c/1329811
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607165}
--
wpt-commits: fde96a64c643c81649f3abe7768be240264df57f
wpt-pr: 14017
Automatic update from web-platform-tests[css-flexbox] ChildIntrinsicLogicalWidth should use fit-content, not max-content
This function needs to match the actual sizing we use. But, since
this is the cross-axis size, we use fit-content:
https://drafts.csswg.org/css-flexbox/#algo-cross-item
See LayoutBox::SizesLogicalWidthToFitContent and LayoutBox::ComputeLogicalWidthUsing
for where we do that fit-content sizing; this code makes us
match the ComputeLogicalWidthUsing calculation.
This bug is currently somewhat hard to trigger because it requires
a combination of all of:
- flex-wrap: wrap
- flex-direction: column
- More than one flex line
- Not using align-items: flex-start or align-content: flex-start
- No explicit width on the flex item
- The max-content width needs to be larger than the width of flexbox
The reason this does not matter in other cases is because we only use
this function to set FlexLine::cross_axis_extent, which we overwrite in
AlignFlexLines if we only have one line. And if we do have more than
one line, we only use this value for aligning items and lines, so
it only matters if we don't use flex-start alignment.
This bug will be much easier to trigger once bug 599828 is fixed (there
are at least two real-world sites that are affected by this once
that bug is fixed)
Bug: 876749
Change-Id: I673026bedfaf0e4c4a25830ef686b200ec8f54a1
Reviewed-on: https://chromium-review.googlesource.com/c/1327746
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607342}
--
wpt-commits: 2281bfa056ad0ca78b9ef60ca2deb0d7f845890f
wpt-pr: 13991
Automatic update from web-platform-tests[css-text] Skip trailing spaces for pre-wrap even if word can be broken
According to the specs, preserved white-spaces should hang, or visually
collapse, when white-space is set to pre-wrap; even if word-break allows
breaing the word at any point.
https://www.w3.org/TR/css-text-3/#line-break-details
Bug: 768363
Change-Id: I7ab356ed6f789ecef087ff469ad97c50e7af49be
Reviewed-on: https://chromium-review.googlesource.com/c/1318694
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#607550}
--
wpt-commits: 9a723ed63038173a788b58fade402c4c4653df3b
wpt-pr: 13946
Automatic update from web-platform-testsAdd action_sequence in testdriver
After we expose test_driver.Actions API to web users, we add their
implementation in our testdriver file, and fix the wpt tests of
Actions API.
Bug: 893480
Change-Id: Ib02c0223208eeb2cc30c2ca35b98d5fc938baa2c
Reviewed-on: https://chromium-review.googlesource.com/c/1289119
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606882}
--
Update infrastructure/metadata/ to match Chrome and Firefox results
--
wpt-commits: 29a37f9c951913bfab45f280d99eaade671fa68f, 683ea003fe4c377eea847e2bccbd13d42c8e030e
wpt-pr: 13640
Automatic update from web-platform-testsServiceWorker: Add new WPT tests to make sure to update a registration
with different script type and identical script content.
These tests check that a registration is updated correctly with
different script type. At first Service Worker is registered as
classic script type, then it is re-registered as module script type,
and vice versa. A main script is identical.
Bug: 824647
Change-Id: I2a3f87da1013f84c6e9495f362899dfe6ab97b45
Reviewed-on: https://chromium-review.googlesource.com/c/1298822
Commit-Queue: Asami Doi <asamidoi@google.com>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604551}
--
ServiceWorker: Deflake update-with-script-type.https.html
To sheriff: Please re-disable the test if it's still flaky.
In this test file, some tests start re-registering the second service worker
before the first service worker gets activated. In my theory, this sometimes
squashes the second registration job into the first registration job, and
results in test flakiness. This CL makes sure the second register runs after
the first service worker gets activated.
Note that it would be the correct behavior that the second registration job
isn't squashed when the script type is changed. There is a spec issue about
this: https://github.com/w3c/ServiceWorker/issues/1358
Bug: 901317
Change-Id: I7ce379071a35ef9aeb98e4492d651ee6fc4714ec
Reviewed-on: https://chromium-review.googlesource.com/c/1328546
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607494}
--
wpt-commits: 5abc7eaa765521804395067e8348e829ac2cb130, 3571d11d7c5201b454c2f3365fae04931ff6c03a
wpt-pr: 13755
When removing an out of flow frame under a multicol subtree, it shouldn't affect
the multicol tree structure. We should instead check the in flow frame's
relationship with the multicol subtree.
Differential Revision: https://phabricator.services.mozilla.com/D11540
--HG--
extra : moz-landing-system : lando
The modification to nsLayoutUtils::GetFirstLinePosition() is needed because we
need to get the correct first line position from child (i.e. ColumnSet) when
there's an outside bullet on ColumnSetWrapperFrame.
The difference between the two newly added tests is "overflow: hidden" on
the columns.
Differential Revision: https://phabricator.services.mozilla.com/D7009
--HG--
extra : moz-landing-system : lando
Removing the inner field while focused nulls out the active element, without a
blur event of course, so this means that we left the :focus state in the input
set incorrectly, plus that we actually lost focus.
Differential Revision: https://phabricator.services.mozilla.com/D12106
--HG--
extra : moz-landing-system : lando
The fast internal reftest harness doesn't work yet, so in the meantime
default to the functional but slower external harness. Also ensure
that the Ahem font is installed by default.
Depends on D12035
Differential Revision: https://phabricator.services.mozilla.com/D12036
--HG--
extra : moz-landing-system : lando
Following the lead of bug 1197716, put the Ahem font into the firefox
profile where it is read by Fennec.
Depends on D12034
Differential Revision: https://phabricator.services.mozilla.com/D12035
--HG--
extra : moz-landing-system : lando
Add a ReftestExecutor implementation matching the one that we use for
Desktop Firefox.
Differential Revision: https://phabricator.services.mozilla.com/D12034
--HG--
extra : moz-landing-system : lando
"request_id" is never defined in the file, and it looks like it should be using "report_id" like most other places in this file.
Differential Revision: https://phabricator.services.mozilla.com/D12195
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsAdd support for running reftests in fennec
Add a ReftestExecutor implementation matching the one that we use for
Desktop Firefox.
Differential Revision: https://phabricator.services.mozilla.com/D12034
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1507532
gecko-commit: 9702f65efe224bcb14f64db9eeb99ca2ad5ef8f8
gecko-integration-branch: central
gecko-reviewers: KWierso
--
Add support for copying Ahem to the installed Firefox profile
Following the lead of bug 1197716, put the Ahem font into the firefox
profile where it is read by Fennec.
Depends on D12034
Differential Revision: https://phabricator.services.mozilla.com/D12035
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1507532
gecko-commit: 32fdcb91c2a51fb572e364d94180631d76a6fb33
gecko-integration-branch: central
gecko-reviewers: gbrown
--
Set up mach defaults to match working wpt android reftest settings
The fast internal reftest harness doesn't work yet, so in the meantime
default to the functional but slower external harness. Also ensure
that the Ahem font is installed by default.
Depends on D12035
Differential Revision: https://phabricator.services.mozilla.com/D12036
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1507532
gecko-commit: 294c7b9011c0a5657ea384d1328805ff48e60f43
gecko-integration-branch: central
gecko-reviewers: KWierso
--
Fixup formatting issue.
--
wpt-commits: 18203d87aa75d4a23ba957ca01a7714e5ee5f238, dd4913a53bf8841dd03ef875bfb82e258d5dbb09, 30eea7feb3af10d91ca14e6735b35bf7e96a856a, be998ebbfc08085f18c1f9ed8d22c52b03134167
wpt-pr: 14104
Automatic update from web-platform-testsFix box-shadow clipping for opaque-background <body>
In the presence of an opaque background,
BoxPainterBase::PaintNormalBoxShadow() insets the shadow clip by one
unit (in order to mitigate seaming artifacs), effectively expanding the
shadow inwards, and relies on the opaque background overdrawing this
inset.
But <body> doesn't paint its own background -- it gets transferred to
the view and painted in a different context => the shadow inset remains
visible.
To address this, pass background-skip information to
PaintNormalBoxShadow(), and disable the inset logic when the background
is not being drawn.
Bug: 899342
Change-Id: I5e04a1c17c2be324bf4c6767d2159372f546cc24
Reviewed-on: https://chromium-review.googlesource.com/c/1336495
Commit-Queue: Florin Malita <fmalita@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#609014}
--
wpt-commits: 44a54b7ededf2dc68fe9b3d2d6f2dca4f1f8372d
wpt-pr: 14067
Automatic update from web-platform-testsViolation reports for 'layout-animations'
This CL adds support for generating violation reports for 'layout-animations'
feature policy. The new implementation triggers a report when:
1- CSS Parser finds usage of @keyframes for one of the banned styles.
2- element.animate() changes a banned style.
Bug: 902836,867471
Change-Id: I79900603eb0166514d7986dc189ec914bd95f899
Reviewed-on: https://chromium-review.googlesource.com/c/1324138
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608984}
--
wpt-commits: b8ac03b76dc36f29c66bef25bc69c322b85dc57c
wpt-pr: 13972
Automatic update from web-platform-testsFix a typo in css/css-text/writing-system/ already fixed in ref (#14097)
The typo in the ref was fixed in
https://github.com/web-platform-tests/wpt/pull/13430, but the test
itself was not updated. That's bad.
--
wpt-commits: 0601d669f54ea46df0c1b08b9927ad6933a06fd3
wpt-pr: 14097
Automatic update from web-platform-testsSVG Geometry: computed value of properties (#14075)
cx cy r rx ry x y computed values are lengths or percentages.
https://svgwg.org/svg2-draft/geometry.html
--
wpt-commits: 39c2331ea623e23849d2f6fc99f804e5e2d374d2
wpt-pr: 14075
Automatic update from web-platform-tests[css-logical] Fix logical values according to the spec
Spec: https://drafts.csswg.org/css-logical/#directional-keywords
Currently logical values compute to the corresponding physical value,
and the mapping is with respect to the element itself. This patch
makes them compute as specified and changes the mapping to be with
respect to the containing block.
BUG=901409
TEST=external/wpt/css/css-logical/logical-values-float-clear.html
TEST=external/wpt/css/css-logical/logical-values-float-clear-reftest.html
TEST=external/wpt/css/css-logical/logical-values-resize.html
TEST=webexposed/nonstable-css-properties.html
Change-Id: Ie0acaacde813c5343ec3bb8de712c4af03639475
Reviewed-on: https://chromium-review.googlesource.com/c/1315989
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608730}
--
wpt-commits: 68eabe4d5bf5bed82dcdcc33e8b9e54a45d55307
wpt-pr: 13928
Automatic update from web-platform-tests[css-grid] Some fixes on grid-container-scrollbar-* tests
* Use Ahem font to avoid weird small pixel differences on iOS.
* Fix some typos reported by @fred-wang at https://bugs.webkit.org/show_bug.cgi?id=191656#c14
--
Merge pull request #14092 from mrego/grid-container-scrollbars
[css-grid] Some fixes on grid-container-scrollbar-* tests
--
wpt-commits: ef7824a8ff88c95d36b31b377fe252f7c56d2da0, 1b543a1083f48c13b25f23a5f23d14f6ade958d4
wpt-pr: 14092
Automatic update from web-platform-testsFetch: test no-cors Headers API better
For https://github.com/whatwg/fetch/pull/833.
--
wpt-commits: ccb1c202a4ad83d88fe9bc133e2816b86e4bcfd2
wpt-pr: 14079
Automatic update from web-platform-testsservice worker: Let register('data://blah') throw a TypeError
register('data://blah') should throw a TypeError instead of SecurityError.
If scopeURL’s scheme is not one of "http" and "https", reject promise
with a TypeError and abort these steps.[1]
[1]: https://w3c.github.io/ServiceWorker/#start-register-algorithm
Bug: 877138
Change-Id: Ic1e8cae52ec9393152044aa37da389eb499165bb
Reviewed-on: https://chromium-review.googlesource.com/c/1189688
Commit-Queue: Amos Lim <eui-sang.lim@samsung.com>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608635}
--
wpt-commits: 64ee30dc4f4c7cd5016ffcfbbb6e1012b978ed66
wpt-pr: 14048
Automatic update from web-platform-testsFix serialization of computed style for 'paint-order'
We were always serializing as the completed (all keywords present) form,
which is not the shortest canonical form.
https://svgwg.org/svg2-draft/painting.html#PaintOrder
Fold the ComputedStyleUtils helper into the PaintOrder CSSProperty
class, since this is very specific to this property.
Matches WebKit and almost Gecko (which seems to handle some "two
keyword" cases differently.)
Bug: 904898
Change-Id: Ib796a111e601485e339fdf2739a587fb5f893b8a
Reviewed-on: https://chromium-review.googlesource.com/c/1335579
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608623}
--
wpt-commits: 8ffe6b78eb915feefba921914f47c40b6f1880e6
wpt-pr: 14077
Automatic update from web-platform-testsCheck including the error message from Error constructor as required
--
wpt-commits: b4c61af0f410976b96279df7f75715091619057d
wpt-pr: 14036
Automatic update from web-platform-tests[UserTimingL3] Fix meature, mark API feature detection
UserTimingL3 uses returned value for feature detection. If measure and mark
API returns null, the APIs are L2 API; If the APIs return an entry, the APIs are
L3 API. However, in the current implementation, when L3 API is enabled, the
APIs do not always return the created entry.
This CL is to fix this bug, and add layout tests to verify it.
Change-Id: I9854f0abd0d64a3334701e09d6ce0fc245fcca3e
Reviewed-on: https://chromium-review.googlesource.com/c/1338225
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608552}
--
wpt-commits: a4efb68eb4bb30453a6c958ad58f8c2540dc967e
wpt-pr: 14084
Automatic update from web-platform-testsAdding more layout/WPT tests for backdrop-filter
These should reproduce (at least) these issues:
- https://crbug.com/622128 - dark areas brought in from edges
- https://crbug.com/632979 - dark areas brought in from edges
- https://crbug.com/659501 - menus cause too much filtering
- https://crbug.com/767997 - menus cause too much filtering
- https://crbug.com/813796 - incorrect border used for filter
- https://crbug.com/593307 - incorrect border used for filter
Bug: 497522,622128,632979,659501,767997,813796,593307
Change-Id: Iafea2fc8fffba950f74d27f21170df647dc62e29
Reviewed-on: https://chromium-review.googlesource.com/c/1330888
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608537}
--
wpt-commits: a2fb878b4b9e4164437357f2bfba4c28e8c0e1ea
wpt-pr: 14026
Automatic update from web-platform-testsKeep animations running going to/from fullscreen.
LazyReattachIfAttached() nukes the computed styles synchronously so that
we are not able to keep animations alive for the next lifecycle update.
Add a bit on Node to say that we need a forced layout tree reattach and
trigger the re-attach from style recalc instead.
Bug: 900162
Change-Id: I22f51f5e091932fc8a63213af88903c7866abbb4
Reviewed-on: https://chromium-review.googlesource.com/c/1333809
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608530}
--
wpt-commits: 9fcbfa0a6c02e373780f897dcf5282907180e49a
wpt-pr: 14034
Automatic update from web-platform-testsAdd report-only mode to Feature Policy
This change adds a "report-only" policy to each security context, which
is local to that context (not replicated across processes) and is used
to determine whether a report should be sent even if a feature is
enabled, when the feature is used.
Reports are now augmented with a "disposition" field, which is either
"enforce", if the feature usage was actually blocked, or "report", if
it was not.
Feature policy directives are placed in the report-only policy if the
feature name is suffixed with "-report-only", otherwise, they affect
the regular (enforcing) policy.
Explainer at
https://github.com/WICG/feature-policy/blob/master/reporting.md
Existing tests are updated, and new tests for report-only mode are
added to ensure that reports are sent even when the feature is used
successfully.
Bug: 904878
Change-Id: I27bc42729c5ab5560160f3d993431e606a8a3a47
Reviewed-on: https://chromium-review.googlesource.com/c/1178811
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608004}
--
wpt-commits: b39f5e0d0e0872cdd9b7592f0b9ff0b5c11bcef3
wpt-pr: 13984
Automatic update from web-platform-tests[LongTasks] Change TaskAttributionTiming name to 'unknown'
At TPAC, we agreed that 'script' is confusing because it implies that
longtasks only measure script work. Thus, we decided to change the name
to 'unknown'. Also see https://github.com/w3c/longtasks/issues/47.
Change-Id: I5a0666d0fa078bfeac8ab6e8397b9b51aca3e833
Reviewed-on: https://chromium-review.googlesource.com/c/1336367
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608479}
--
wpt-commits: 4309ceb7b165a42534514ca9933846cc0912bdae
wpt-pr: 14063
Automatic update from web-platform-testsImprove robustness of wpt animation interpolation tests.
This patch fixes the problem where subtle changes to numerical values in matrix interpolation cause mismatches in the expected results.
To address the issue:
* Styles are checked to see if they are of the form matrix(...) or matrix3d(...).
* If the style is a matrix, then arguments are rounded and the style is reconstructed.
Bug: 797472
Change-Id: I44d6e0ed13e24dc2ecfeeacbcd4809d6dcdb6465
Reviewed-on: https://chromium-review.googlesource.com/c/1337640
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608466}
--
wpt-commits: 794b7ee9292f09802cd41e41a04be420b1d7bec3
wpt-pr: 14080
Automatic update from web-platform-tests[css-flex] align-content should apply even when there's just a single line
In Jan 2015 the spec changed in
https://drafts.csswg.org/css-flexbox/#change-201409-align-content-wrapping
Change our code accordingly. This effectively reverts commit
crrev.com/290823003 and relands crrev.com/2191683003
align-content-wrap-004 is a test for bug 641789, which was a regression
from the previous attempt at landing this patch.
Bug: 599828
Change-Id: I8de127c19203854922eb23a626cee4de9a772f22
Reviewed-on: https://chromium-review.googlesource.com/c/1323906
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608449}
--
wpt-commits: 34ecd56f063821c113fd20bcb05b80aafd82d787
wpt-pr: 14062
Automatic update from web-platform-testsFloats in a next fragmentainer may push lines down.
We cannot assume that when we push a line to the next fragmentainer
(because it doesn't fit in the current one), the line is going to fit
there. If the next fragmentainer has a float that nothing fits beside
and the float is too tall to fit the line below it, we need to jump to
yet another fragmentainer in order to find room for the line.
Bug: 902762
Change-Id: Ied14694ed1ad4fc25d28527edd1ca7389f00664c
Reviewed-on: https://chromium-review.googlesource.com/c/1335580
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608414}
--
wpt-commits: a218e2f1678badf75722fd444524d98cd5996b3f
wpt-pr: 14058
Automatic update from web-platform-tests[css-properties-values-api] Validate var() fallbacks.
According to a recent spec edit, any fallback in a var()-reference must
match the syntax of the referenced property, otherwise the var()-reference
is invalid. This applies even if the fallback is not used.
To implement this, ResolveFallback now returns kNone/kFail/kSuccess instead
of a bool. This is necessary, because the kNone case may be both an error
state and a success state, depending on whether the fallback is being
used or not, hence a plain bool is not sufficient.
R=futhark@chromium.org
Bug: 641877
Change-Id: I951eef6335bf1cd4064d59959d73ec4fa39c9ee0
Reviewed-on: https://chromium-review.googlesource.com/c/1335576
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608365}
--
wpt-commits: 4bf9cbfa246859a47e46507154760526e48f8af0
wpt-pr: 14055
Automatic update from web-platform-testsRevert "Update infrastructure/metadata/ to match Chrome and Firefox results"
This reverts commit c2bf7c6ed9e3ab9d42000b712d3793f6b58c33cd.
--
Revert "Add action_sequence in testdriver"
This reverts commit 3287351b606c4588e397632e2ab04641dc91094d.
--
wpt-commits: 9e10da29c88d1268b65bac176df3c6ab2ee6a3d5, 02dccc6b5ad45352ae5c3bdf23fcbd9b0deea071
wpt-pr: 14076
Automatic update from web-platform-testsRemove timeout in async_test for IndexedDB tests
Remove all the timeout parameters in async_test for IndexedDB tests.
Affected tests: 44, Pass: 44, Failed: 0
Related: #11120
--
wpt-commits: c7c8c373d49baba4721e7800525b1699bf67ac7e
wpt-pr: 14068
Automatic update from web-platform-tests[testharness.js] Honor test config in workers (#14061)
Ensure that uncaught exceptions originating from workers do not
influence harness status when the `allow_uncaught_exception` setting has
been enabled.
--
wpt-commits: 0ddb31913184805fa3725e22e5b88046e961996b
wpt-pr: 14061
Automatic update from web-platform-testsReplace direct use of offerToReceiveAudio by generateAudioReceiveOnlyOffer.
This allows to use non legacy APIs by default if supported.
--
Merge pull request #14040 from youennf/remove-offerToReceiveAudio-use-outside-legacy
Replace direct use of offerToReceiveAudio by generateAudioReceiveOnlyOffer
--
wpt-commits: 27e0acb4312abf064d6491ff29db3852a958dff8, 42abd6cc7ebd7c0b0513639e1a8c1bd958638fed
wpt-pr: 14040
Automatic update from web-platform-testsFix wpt: service-worker/navigation-redirect.https.html
As preparation for adding FetchEvent#resultingClientId, this CL fixes
the test to make it pass once resultingClientId is impelmeneted.
Bug: 778497
Change-Id: I6309a13d4315e6a99149275a6d7889f14ce0d757
Reviewed-on: https://chromium-review.googlesource.com/c/1335055
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608167}
--
wpt-commits: 6856483bcc86322198f10e0c42385a7f9127eb66
wpt-pr: 14050
Automatic update from web-platform-tests[css-grid] Consider scrollbars in PopulateGridPositionsForDirection()
We never care about scrollbars
in LayoutGrid::PopulateGridPositionsForDirection(),
that's fine if the scrollbars are at the end
(e.g. on the right in horizontal writing mode and LTR direction)
but it causes problems when they're at the beginning
(e.g. on the left in horizontal writing mode and RTL direction).
The patch modifies the method so it takes into account scrollbar size
in order to compute the position of the columns/rows
depending on the direction and the writing mode.
BUG=904438
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-lr-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-rl-001.html
Change-Id: I9c8307638647e449f6975cacf99f89e29d4fa655
Reviewed-on: https://chromium-review.googlesource.com/c/1334370
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#608154}
--
wpt-commits: ca8728e002fdfcdde1ee2efd39ebaccc823bf9b2
wpt-pr: 14052
Automatic update from web-platform-testsWorklet: Modernize service worker interception tests for worklets using async/await
This is just a cleanup CL, and there're no functional changes.
Bug: n/a
Change-Id: I60820045469eed4a0903b37af9e4f8927bcc884d
Reviewed-on: https://chromium-review.googlesource.com/c/1335047
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607892}
--
wpt-commits: d16eb1ce23500e7234f58df86a59d5c00d222118
wpt-pr: 14045
Automatic update from web-platform-tests[wptserve] Eliminate race condition (#14024)
This race condition was expressed during testing sessions where the
first test to use the Stash feature issued did so with multiple requests
made in parallel.
--
wpt-commits: cbb25e2c99696956ed2a36e7bcdbdee1dca71705
wpt-pr: 14024
The caches weren't being invalidated when the manifest itself
changed. To fix this the manifest itself has to be written before the
cache and the cache has to include data about the manifest that it's
associated with (the mtime and path are used for this purpose).
To make all this work requires a single method that can load the
manifest, update it, write the manifest and write the
caches. Therefore we introduce a single load_and_update method that is
intended to replace all previous use of the load() or update() methods
(and as a bonus handles manifest version mismatches in a single
place).
Depends on D8227
Differential Revision: https://phabricator.services.mozilla.com/D8228
--HG--
extra : moz-landing-system : lando
Compared to the normal os.walk this has a couple of differences:
* It returns lists of (name, stat) for filenames and directories,
allowing callers to reuse the stat data without going back to the
system to re-request it.
* Directories are always returned as paths relative to the root, and
the root itself is returned as the empty string.
* It is non-recursive.
There are also a few features missing that aren't required for our use
cases.
Depends on D8226
Differential Revision: https://phabricator.services.mozilla.com/D8227
--HG--
extra : moz-landing-system : lando
When processing the manifest using the worktree, instead of reading
all files to see if the content changed, instead only process files where
the mtime has been updated since the previous run. Also cache the
result of running gitignore, so we can save a couple of seconds
processing the gitignore rules.
Depends on D8225
Differential Revision: https://phabricator.services.mozilla.com/D8226
--HG--
extra : moz-landing-system : lando
This updates the gitignore implemenation to take input like os.walk
but with additional stat data for the files. It also makes several
useful optimistaions:
* Avoid using regex when just matching a literal
* Identify patterns that can only match the final component of a path
and run those against that component rather than the full path.
* Add the possibility of providing a dictionary of paths to gitignore
statuses as a cache.
This dramatically reduces the amount of time we spend in gitignore
processing when updating the manifest.
Depends on D8223
Differential Revision: https://phabricator.services.mozilla.com/D8224
--HG--
extra : moz-landing-system : lando
We end up with a lot of rules like (?:.*)/.*\.ext which are basically
trying to find the last component in a path and match against
that. These are rather slow to run so the easiest thing tdo is just
pass in the last component of the path when we know that's the only
thing the rule can match.
The changes to surrounding code to use this API will be made in future
commits.
Depends on D8222
Differential Revision: https://phabricator.services.mozilla.com/D8223
--HG--
extra : moz-landing-system : lando
- Expose FetchEvent.resultingClientId on non-subresource, non-"report"-destination requests.
- Delay Clients.get(FetchEvent.resultingClientId) resolution until the resulting client is execution ready.
- Add WPTs to test for existence of resultingClientId and Clients.get promise resolution values.
Differential Revision: https://phabricator.services.mozilla.com/D5333
--HG--
extra : moz-landing-system : lando
This patch removes the dom.webcomponents.shadowdom.enabled pref and all its
references, including the following functions:
* nsContentUtils::IsShadowDOMEnabled()
* nsIDocument::IsShadowDOMEnabled()
* nsDocument::IsShadowDOMEnabled(JSContext* aCx, JSObject* aGlobal)
* nsDocument::IsShadowDOMEnabled(const nsINode* aNode)
* nsTextNode::IsShadowDOMEnabled(JSContext* aCx, JSObject* aObject)
This function is renamed and updated to nsDocument::IsCallerChromeOrAddon():
* nsDocument::IsShadowDOMEnabledAndCallerIsChromeOrAddon(JSContext* aCx, JSObject* aObject)
I didn't change the tests that load Shadow DOM tests in an iframe, in the interest of keeping hg annotation history.
Differential Revision: https://phabricator.services.mozilla.com/D11183
--HG--
extra : moz-landing-system : lando
This patch introduces 2 new prefs:
- devtools.console.stdout.chrome: if true, console API writes on stdout when
used by chrome code
- devtools.console.stdout.content: console API write on stdout when used by
content code.
Automatic update from web-platform-testsRe-plumb backdrop-filter through blink-gen-property-trees
With this CL, backdrop-filter will continue to work when the
--enable-blink-gen-property-trees flag is enabled. Behavior should be
identical to behavior without the flag.
Also, I added a number of layout/WPT tests for backdrop-filter,
some of which currently pass, and some of which need fixing. The ones
that need fixing have been added to TestExpectations. These new tests
should reproduce (at least) these issues:
- https://crbug.com/314867 - respecting isolation
- https://crbug.com/525099 - respecting isolation
- https://crbug.com/547937 - border radius
- https://crbug.com/524689 - filter plus backdrop-filter
- https://crbug.com/745012 - boundary effect problems
I also moved the existing tests out of external/wpt/css/css-filter
into external/wpt/css/filter-effects, where they really should be,
now that filter-effects is being pulled into the tree.
Bug: 497522,314867,525099,547937,524689,745012
Change-Id: I2be33fbc0e17dec2cd138f9796971fb4a9a57216
Reviewed-on: https://chromium-review.googlesource.com/c/1316661
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607447}
--
wpt-commits: e1bde44cb56120f187d326557a681f87b31b43af
wpt-pr: 14008
--HG--
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-001.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-001.html
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-002.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-002.html
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-ref.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-block-is-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-block-is-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-block-is-container.html => testing/web-platform/tests/css/filter-effects/filtered-block-is-container.html
rename : testing/web-platform/tests/css/css-filter/filtered-html-is-not-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-html-is-not-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-html-is-not-container.html => testing/web-platform/tests/css/filter-effects/filtered-html-is-not-container.html
rename : testing/web-platform/tests/css/css-filter/filtered-inline-is-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-inline-is-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-inline-is-container.html => testing/web-platform/tests/css/filter-effects/filtered-inline-is-container.html
Automatic update from web-platform-testsHTMLScriptElement text attributes modified to accept TrustedTypes
HTMLScriptElement::text() and setText() functions modified to accept
TrustedScript as an argument.
Added HTMLScriptElement::innerText and HTMLScriptElement:textContent
attributes to override existing implementations in HTMLElement
and Node, and to accept TrustedScript.
Changed HTMLElement::innerText and Node::textContent .idl definitions
and adjusted setters and getters to accept TrustedScript.
Bug: 739170
Change-Id: I63da5714ffac328c6ae2f76e5da58c05f44a1cbf
Reviewed-on: https://chromium-review.googlesource.com/c/1178046
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607232}
--
wpt-commits: 860091dbc783a678f128328646a519d9891f0838
wpt-pr: 12531
Automatic update from web-platform-testsAdd unit tests for wrapper handlers in tools/serve
Add unit tests for all kinds of wrapper handlers in tools/serve/serve.py.
See #12452
--
Update the unit tests
* Fix the import error
* Improve the code style
--
Read and write files in binary mode
Read and write files in binary mode so the unit tests can pass in
Python3 environment.
--
wpt-commits: 2225031efc850d3b87ea33210b79730b466f5c50, dfbb0fd0cba67a8b0ea261fcfaaa805fe6ed7f03, d0c94e610154d3a7cdf1f2882a7ac74d4dfe3114
wpt-pr: 14004
Automatic update from web-platform-testsSet orphans and widows to 1 in new multicol test.
The test left orphans / widows at their initial value (2), but did
assume that we could freely break wherever we wanted. Blink honors
orphans and widows requirements inside multicol containers, so set
them to 1, to get the behavior that the test expects.
Bug: 904263
Change-Id: Ia138da5c65b1c5da450441f38e033320bc983a94
Reviewed-on: https://chromium-review.googlesource.com/c/1331389
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607211}
--
wpt-commits: 0d4f539f5d4c7272c9fe07bd204674b207e4a979
wpt-pr: 14021
Automatic update from web-platform-testsTypo: "opoacity" should be "opacity" (#14018)
--
wpt-commits: 2f868fae5b43c68e4807f6a4ec9487f13ea39cf4
wpt-pr: 14018
Automatic update from web-platform-testsMIME types: test 0x0B, 0x0C, and newlines
For https://github.com/whatwg/mimesniff/pull/90.
--
wpt-commits: 6aeb68e38a61c2e332a7592f5cad640cf58b73f2
wpt-pr: 13615
Automatic update from web-platform-tests[css-text] Advance width of a tab must be at least 0.5ch
Relates to https://github.com/w3c/csswg-drafts/issues/2883
--
Merge pull request #13336 from frivoal/text-2883
[css-text] Advance width of a tab must be at least 0.5ch
--
wpt-commits: 3e89195978753b5e77a4aa04b420d17eb20dddd8, 67fe8ce363b1e2981d322e0a1a10186062e26e64
wpt-pr: 13336
Automatic update from web-platform-testsRemove ES6 object matching shorthand notation from WebDriver tests (#14015)
This change is to allow older user agents that do not support ES6
constructs to run the WebDriver tests.
--
wpt-commits: fc1a5b73230225faf32bfb85f3928ce154211b0a
wpt-pr: 14015
Automatic update from web-platform-testsSnap at ScrollIntoView.
According to the spec,
https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-386154394
scrollIntoView should
1) Always snap to the target element's snap alignment, and
2) All the affected scrollers should also land on a snap position if
one exists.
This patch does part 2). Before a scrollable_area is added to
the smoothScrollSequencer with its new scroll_offset, we will check if
it has a valid snap offset around, and update the final offset
accordingly.
We'll implement part 1) in a separate patch.
Bug: 842317
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ica22134ed0b1f9d36f5a017c8dd0be54e907dd3d
Reviewed-on: https://chromium-review.googlesource.com/c/1188746
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607019}
--
wpt-commits: a0610cf468e6208e74b2cfda77a565ab90fbd74e
wpt-pr: 13038
Automatic update from web-platform-testsgrid-template-areas serialization
strings in grid-template-areas are normalized, e.g. collapsing
whitespace to a single space, and collapsing repeated periods ('.')
to a single period.
https://github.com/w3c/csswg-drafts/issues/3261#issuecomment-436828363
--
Merge pull request #13977 from ewilligers/grid-template-areas-serialization-2
grid-template-areas serialization
--
wpt-commits: da90a07f543e3307b53230a1f0a2e8b6dc72b42b, a27659a86371bb2d98e622f4e57b85a546898ade
wpt-pr: 13977
Automatic update from web-platform-testsNEL: Generate reports in HTTPNetworkTransaction
Piece by piece, we are moving the Reporting and NEL processing code from
URLRequest and friends into HTTPNetworkTransaction, to make sure that we
produce reports for network requests as defined by the spec.
This patch moves the generation of the actual NEL reports, and includes
some new WPT test cases that verify that we create reports correctly for
redirects and cached responses.
TBR=msramek@chromium.org
Bug: 895823
Change-Id: Ie8e17a2a2b3571a7cdfd39057da486f5ad2c9f6f
Reviewed-on: https://chromium-review.googlesource.com/c/1318169
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Reviewed-by: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606958}
--
wpt-commits: 9902fbae9124fb565389983e49235d82cf429242
wpt-pr: 14007
Automatic update from web-platform-testsbrowser.py code cleanup
Some code cleanup that was recommended in https://github.com/web-platform-tests/wpt/pull/13185
--
wpt-commits: 7c568fdbd98ccdb92152c14521d3cc8c729a45a2
wpt-pr: 13239
Automatic update from web-platform-testsAdd a wpt create command
wpt create makes a file with the required elements for a test, and
optionally opens it in an editor.
--
wpt-commits: 726725be8f98607d521632e595fe5f2054570158
wpt-pr: 13701
Automatic update from web-platform-testswebkitRelativePath preserves common ancestors (#13988)
Drop requirement that webkitRelativePath only provides the shortest common ancestor, which matches behavior in Edge/Safari/Firefox, and soon Chrome.
Spec change: e6b848f4dc
Tracking issue: WICG/entries-api#18
--
wpt-commits: 378b79a9cd09df75403d88828d1793bb720a9488
wpt-pr: 13988
Automatic update from web-platform-testsWire the resizeMode property to the constraints parsing mechanism.
This CL adds resizeMode support for MediaStreamTrack.getConstraints()
and marks resizeMode as a supported constrainable property.
Support for getUserMedia(), applyConstraints() and getCapabilities()
will be added in follow-up CLs in this series.
Intent to Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/V2srjdzRCXE
Bug: 854980
Change-Id: Ia23b8119768ab67ab498f0f8e2267aeb388f9fc3
Reviewed-on: https://chromium-review.googlesource.com/c/1309749
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606856}
--
wpt-commits: 055077093043d235040d20ae60458ee5ac6cded5
wpt-pr: 13846
Automatic update from web-platform-testsSetup logging earlier in the wpt run startup.
Curerntly we wait until we're setting up wptrunner kwargs to create the logger.
But that's pretty silly; we should set up the logger first thing and then use it
consistently to log during the setup phase.
--
wpt-commits: 47f0061f15dd2973dab11d87c03f0c8264d32e02
wpt-pr: 13578
Automatic update from web-platform-testsDo not send old capabilities to ChromeDriver
The configuration for Chrome currently sends 'platform' and 'version'
capabilities to ChromeDriver. These capabilities are non-standard and
unnecessary, and will cause errors when ChromeDriver becomes more
standard compliant.
--
wpt-commits: 7d9070444977a83af886d73bf80d57096be70ca5
wpt-pr: 13995
Automatic update from web-platform-testsFetch: CORS and request's Content-Type header
For https://github.com/whatwg/fetch/pull/829.
--
wpt-commits: eed621bc2f995bced9481df2cead4c4632c72cdd
wpt-pr: 13921
Automatic update from web-platform-testshtml: Fix a sanitization issue of type-change-state.html
type-change-state.html assumed sanitized value for " foo\rbar " was
fixed per a input type, and it was specified by 'sanitizedValue' field.
However, it depends on the previous type. For example, the new input
types of the following A and B are same, initial value setter arguments
are same, but sanitized values of A and B should be different due to the
sanitizer difference between 'hidden' and 'url':
A)
input.type = "hidden";
input.value = " foo\rbar ";
// input.value is " foo\rbar "
input.type = "text";
// input.value is " foobar ".
B)
input.type = "url";
input.value = " foo\rbar ";
// input.value is "foobar"
input.type = "text";
// input.value is "foobar".
This CL fixes this issue by replacing 'sanitizedValue' field with
'sanitizer' field, which specifies a simple sanitizer implementation.
This fixes five test cases, which have failed with all major browsers.
Change-Id: I1b5f75e610138b1d117e93723471427ee655c300
Reviewed-on: https://chromium-review.googlesource.com/c/1326203
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606730}
--
wpt-commits: 3cd60908e05beed166359907018c2abe238cb205
wpt-pr: 13993
Automatic update from web-platform-tests[media] Treat cross-origin redirect as TAINTED only for no-cors requests
With https://crrev.com/a9cbaa7a40e2b2723cfc2f266c42f4980038a949,
WebMediaPlayer blindly treats a resource experiencing cross-origin
redirects as TAINTED. In fact, it should be treated as TAINTED only
when its request mode is "no-cors".
The added tests are provided by hongchan@chromium.org.
Bug: 899745, 901383
Change-Id: Idb66407552085b053818f3e4a9d8d5ff3ddeaf45
Reviewed-on: https://chromium-review.googlesource.com/c/1325281
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606681}
--
wpt-commits: d5be80a86d4f938250c075ac12414ad47516969c
wpt-pr: 13980
Automatic update from web-platform-testsReland "Make XR FrameData and Environment mojo associated"
This is a reland of 126a1168e3bcffb43c706822b3aa28695840310f
The fix in this change addresses compile errors on the
Oculus platform.
TBR=dcheng@chromium.org
dcheng@chromium.org: please review, though there are no
new changes to vr_service.mojom
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
Bug: 867057, 876135, 843376
Change-Id: If76578ebabbb40d03a21f6f557c5d4c27f69fc38
Reviewed-on: https://chromium-review.googlesource.com/c/1324089
Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606643}
--
wpt-commits: a516e7edca11e2efe462d2bfc83b5b88dd9f4072
wpt-pr: 13969
Automatic update from web-platform-testsThe computed value of float with absolute positioning when there is no box should be "none" (#13958)
https://github.com/w3c/csswg-drafts/issues/1436
--
wpt-commits: 4477b9d2fadaca4314a9fc7d88ab6db6ad47a321
wpt-pr: 13958
Automatic update from web-platform-testshtml: Fix an issue of type-change-state.html about selectionDirection="none"
type-change-state.html contains assertions for the following operation in [1]:
> ..., and set its selection direction to "none".
However it had an issue that the assertions checked if
input.selectionDirection was "none". According to [2],
input.selectionDirection can be "forward" on specific platforms.
> update the element's selection direction to the given direction, unless
> the direction is "none" and the platform does not support that direction;
> in that case, update the element's selection direction to "forward".
[1] https://html.spec.whatwg.org/multipage/input.html#the-input-element:set-the-selection-direction
[2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#set-the-selection-direction
Change-Id: Idc1a97fbb2036e351a788a1f758b3239308d8c71
Reviewed-on: https://chromium-review.googlesource.com/c/1322264
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606310}
--
wpt-commits: 603b17f321fe4275050c59c87b1f3a29a33e9c96
wpt-pr: 13978
Automatic update from web-platform-tests[streams] Add tests for aborting pipeTo()
Add tests for aborting ReadableStream.prototype.pipeTo using an
AbortSignal.
Tests correspond to PR whatwg/streams#744.
--
wpt-commits: 349d41838068164e37a1cbd1c8c6ffeba4c72177
wpt-pr: 13358
Automatic update from web-platform-testsWindow onerror is not triggered bug fix
As pointed out in the bug, unhandled errors on worker threads were not
properly being propagated for the parent thread to handle as the spec
requires (https://html.spec.whatwg.org/multipage/workers.html#runtime-script-errors-2).
This fix adds in the code to do that.
Bug: 685303
Change-Id: Ie3e7ec03153a43efdc6e70b874d6b1a1d8ac35ef
Reviewed-on: https://chromium-review.googlesource.com/c/1287208
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605857}
--
wpt-commits: 920e3b1051f7bcb1fff98417cf91c904dbbdd36a
wpt-pr: 13691
Automatic update from web-platform-testswebkit: add support for the WPE port (#13863)
WPE port is closely related to the GTK port, using the same WebDriver
implementation as well as similar testing-purpose browser application.
Much of the capabilities dictionary construction can thus be the same.
--
wpt-commits: 89692eac0360247e56ba1ae4c32ea38cf1b6a9a0
wpt-pr: 13863
Automatic update from web-platform-testsEnsure that lone surrogates don't appear in wptreport json (#13828)
Python will happily handle "string" data containing codepoints in the surrogate
range. In the JSON output these are always escaped and appear as \uD800 or
similar. That's pretty unfortunate for interop since other languages don't
necessarily support such codepoints not representing a character in the
unicode set in their normal string type. Although it's possible to clean this
up on import it seems more reasonable to ensure that our primary interchange
format is unicode-clean. Therefore this change starts escaping lone surrogates
using the U+ notation so that \uD800 becomed U+D800.
Because Python, this requires two implementations. In UCS4 Python we know that
only lone surrogates should appear in string data; characters outside the BMP
will be represented as a single internal character (*technically* this is
untrue since someone may manually create a string containing a sequence of
surrogates that happens to form a pair; we don't care about handling this
case other than as two unpaired surrogates that happen to be adjacent). In
UCS2 Python surrogates appear in the string data literally, so we need to
check each time we encounter one whether it's a low surrogate followed by
a high surrogate and not escape in that case.
--
wpt-commits: 275904c8b770d10a9d67f6786b75dd4461a9a932
wpt-pr: 13828
Automatic update from web-platform-testsupdate wpt feature policy tests, making them long tests
Bug: 829921
Change-Id: Ia2c70c62d4a4235b21996bbd185746080e1efa35
Reviewed-on: https://chromium-review.googlesource.com/c/1320010
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606045}
--
wpt-commits: 1a7cb3deb6c8661e4cf245a7ffc3e324fb6795f2
wpt-pr: 13954
Automatic update from web-platform-testswebkit: provide port name as run info (#13862)
For the WebKit product, include the port name inside the run info, under the
'webkit_port' key. This will come in handy when disabling tests in metadata files
for specific ports.
--
wpt-commits: 9b9cf22d132ce60af8ad1801fd347965a1a96bae
wpt-pr: 13862
Automatic update from web-platform-tests[ci] Complete Docker image update (#13960)
A recent patch updated the Docker image used by Taskcluster when
building the project's `master` branch [1]. Update the corresponding
configuration for tasks triggered by pull requests. This improves parity
between the two processes, and because the new image is based on a more
recent LTS release of Ubuntu, it reduces the likelihood of errors due to
outdated system dependencies.
[1] https://github.com/web-platform-tests/wpt/pull/13676
--
wpt-commits: 3b729257c88fc09f200993317b6b84c9ae0aee3b
wpt-pr: 13960
Automatic update from web-platform-tests[Azure Pipelines] Document "Build pull requests from forks of this repository" (#13952)
--
wpt-commits: e0e8196c242c8fb1d2a62c13f23455a9d03bd4bb
wpt-pr: 13952
Automatic update from web-platform-tests[filter-effects] Parsing of backdrop-filter (#13871)
Test parsing, serialization and computed value for backdrop-filter
https://drafts.fxtf.org/filter-effects-2/#BackdropFilterProperty
--
wpt-commits: 208508bfdb7a8a9692394488bec2237102e16962
wpt-pr: 13871
Automatic update from web-platform-tests[LayoutNG] Fix vertical-align: text-top in quirks mode
When in quirks mode and there are no text siblings; e.g.:
<div><img><span>text</span></div>
and 'vertical-align: text-top' applied to <img> hits
DCHECK failure and results in incorrect position.
The test ensures that results are the same with the standard
mode.
Bug: 901123
Change-Id: I30564c66d5847f09caf3672ba3d456c0eb798d3e
Reviewed-on: https://chromium-review.googlesource.com/c/1320529
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605965}
--
wpt-commits: 48c278aad9f1570f14e47472e7cf304865602192
wpt-pr: 13962
Automatic update from web-platform-testsfix video reference in webvtt rendering tests
--
wpt-commits: c94bfaa0f97be784245d5c5405ebf2cae78df2f7
wpt-pr: 13553
Automatic update from web-platform-testsFix RTCRtpTransceiver direction tests (#13914)
* Update RTCRtpTransceiver setDirection to direction setter
* Fix currentDirection in RTCRtpTransceiver-direction.html
* Add negative test for setDirection
--
wpt-commits: d37a815dbca209eafc8eb71cb59ce59f4e66f975
wpt-pr: 13914
Automatic update from web-platform-testsRemove support for supportedTypes in Payment Request (#13858)
--
wpt-commits: 615bb572c95add74ca4fb9fed4af5269a49cf4ef
wpt-pr: 13858
Automatic update from web-platform-testsAdded mechanisms for default policy
With a default policy defined, assignments implicitly call createXXX on the default policy
Added ScriptState* to the accessors visible from JavaScript
Tests were updated to check string assignment when trusted-types are needed before and after the default policy is defined
Bug: 739170
Change-Id: I9bb841d69f324b841602d41abd71f753a9858af8
Reviewed-on: https://chromium-review.googlesource.com/c/1207530
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605720}
--
wpt-commits: 24373750793a107c28dbfde50d61cfae192fb485
wpt-pr: 12952
Automatic update from web-platform-testsRun py36-flake8 also for tools/wpt/ (#13947)
--
wpt-commits: bfc7ce508b754e84e95830c2186f1fa8eb9f179e
wpt-pr: 13947
Automatic update from web-platform-testsRevert "Make XR FrameData and Environment mojo associated"
This reverts commit 126a1168e3bcffb43c706822b3aa28695840310f.
Reason for revert: Broke compile: https://logs.chromium.org/logs/chromium/bb/chromium.chrome/Google_Chrome_Win/39908/+/recipes/steps/compile/0/stdout
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
TBR=dcheng@chromium.org,klausw@chromium.org,billorr@chromium.org,lincolnfrog@chromium.org
Change-Id: I7a2408629460f456bf1189acdb0837f7d22a7919
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 867057, 876135, 843376
Reviewed-on: https://chromium-review.googlesource.com/c/1318805
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Commit-Queue: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605551}
--
Merge pull request #13939 from web-platform-tests/chromium-export-0ef86cd598
Revert "Make XR FrameData and Environment mojo associated"
--
wpt-commits: 97ef8fa350d0b1cf5c4692a71b1040d66266e7b7, b306f085d1a008b7636b60efa67a5b89d1fc2f52
wpt-pr: 13939
Automatic update from web-platform-testsFix and re-enable simplecall-no-ssrcs.https.html.
With the changes, the test should pass regardless of if the Chrome or
Firefox behavior is used for what to do when no MSIDs are signaled.
Follow-up work is needed to test both the case of "a=msid:-" and no
"a=msid" line whatsoever, awaiting spec issue to be resolved:
https://github.com/w3c/webrtc-pc/issues/2027
// Relying on fippo's approval to land.
TBR=hta@chromium.org
Bug: 901711
Change-Id: Icaf089d206413510aadad54a0c10b2674450385a
Reviewed-on: https://chromium-review.googlesource.com/c/1319612
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605678}
--
wpt-commits: bce2269d0f17d2a89247895cbee21530ae83c96e
wpt-pr: 13950
Automatic update from web-platform-tests[presentation-api] Revise the test for reconnecting multiple presentations (#13196)
Test closing and reconnecting to multiple connections simultaneously
--
wpt-commits: 7a51b509430cc115df632608356999fa18ac4491
wpt-pr: 13196
Automatic update from web-platform-testswebrtc: rename DTLSTransport.transport to .iceTransport (#13915)
test for https://github.com/w3c/webrtc-pc/pull/2017
--
wpt-commits: c05700b258089fd547808c54707cdc3a64b48344
wpt-pr: 13915
Automatic update from web-platform-testsRemove the "W3C WebSocket API" prefix from websockets/ tests (#13478)
This prefix doesn't add any useful information, and isn't used in all
tests in this directory. Noticed because of the screen real estate it
takes up in a view like this:
https://wpt.fyi/results/websockets/Send-binary-65K-arraybuffer.any.html
In the directory, this command was run, on macOS:
git grep -lF 'W3C WebSocket API - ' | xargs sed -i '' 's/W3C WebSocket API - //g'
--
wpt-commits: 1e747acc90ecdbd23ef3348a144b77696cced55b
wpt-pr: 13478
Kent Tamura
Christian Biesinger
Javier Fernandez
moz-wptsync-bot
Asami Doi
Mike West
Brindusan Cristian
Ting-Yu Lin
Thomas Nguyen
Cosmin Sabou
Gurzau Raul
Luke Wagner
Sebastian Hengst
Emilio Cobos Álvarez
James Graham
Bogdan Tara
Csoregi Natalia
Wes Kocher
youennf
Oriol Brufau
Anne van Kesteren
Fredrik Söderquist
Florin Malita
Ehsan Karamad
Steve Anton
Philip Jägenstedt
Eric Willigers
Eric Willigers
Manuel Rego Casasnovas
Asami Doi
Amos Lim
CYBAI
Liquan(Max) Gu
Mason Freed
Rune Lillesveen
Ian Clelland
Nicolas Pena
Kevin Ellis
Morten Stenshorne
Anders Hartvoll Ruud
Josh Matthews
Automat af Gränssnitt
qiuzhong
jugglinmike
Florian Rivoal
Youenn Fablet
Makoto Shimazu
Hiroki Nakagawa
Andrea Marchesini
Ahilya Sinha
Perry Jiang
Andrew McCreight
arthur.iakab
Timothy Guan-tin Chien
Mats Palmgren
Cristina Coroiu
Andreea Pavel
Razvan Maries
Valentin Gosu
Jonathan Kingston
Daniel Vogelheim
Antoine Quint
Joshua Bell
Mark Roberts
jimevans
Sandra Sun
Douglas Creager
Dominic Farolino
Guido Urdaneta
Luke Bjerring
John Chen
Yutaka Hirano
Max Rebuschatis
aestes
pyup.io bot
François REMY
L. David Baron
Adam Rice
Rayan Kanso
Žan Doberšek
Luna Lu
Geoffrey Sneddon
Koji Ishii
Gary Katsevman
Charles Vazac
Marcos Cáceres
Jan-Ivar Bruaroey
Dmitry Titov
Henrik Boström
Tomoyuki Shimizu
Philipp Hancke