Automatic update from web-platform-testsDevice Sensor: Remove placeholder enumerator values in the sensor::SensorType
According to the mojo style guide:
https://chromium.googlesource.com/chromium/src/+/master/docs/security/mojo.md#do-not-define-placeholder-enumerator-values
It is recommended not to define placeholder enumerator values. Currently,
sensor::SensorType defines two such values: FIRST and LAST. This CL removes
these two placeholder values.
Bug: 870781
Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I8b275bc5680c8c0d97fe2e7208301d6f33236cbe
Reviewed-on: https://chromium-review.googlesource.com/1197423
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588678}
--
wpt-commits: bdf21e69ffaeb96097dfbc0888e4d9eb5413fed2
wpt-pr: 12769
Automatic update from web-platform-testsdocument.open(): Test non-fully active documents (#12770)
For https://github.com/whatwg/html/pull/3977.
--
wpt-commits: 61bc4ecc726596e5ce8634752e09a5e8a20e060f
wpt-pr: 12770
Automatic update from web-platform-tests[Background Fetch] Record via UMA whether a fetch has duplicate requests
Also reject the registration if that happens with a warning, and add a
failing WPT test.
Bug: 871174, 780025
Change-Id: Ibdcc49bc47ea959e0c255a48f5d090cb865a6e45
Reviewed-on: https://chromium-review.googlesource.com/1202262
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588614}
--
wpt-commits: 98c37ef258eb21fb1c3dbf508437e58be21c2145
wpt-pr: 12830
Automatic update from web-platform-testsbindings: Set function name for attribute accessors
This aligns the behavior with the current Web IDL specification as well as
Firefox and Safari.
Bug: 878074
Change-Id: Ia862c1d0d8319fb78726817b69f9151e5fb500fd
Reviewed-on: https://chromium-review.googlesource.com/1191727
Commit-Queue: Timothy Gu <timothygu@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588544}
--
wpt-commits: 31f62ee2b6103a94aafa6ffd5e205c8898f4b9ba
wpt-pr: 12765
Automatic update from web-platform-testsRemove kereliuk from suggested reviewers (#12829)
I'm no longer working on WPT to focus on a new project.
--
wpt-commits: a0f75fcad81bee1dbe35d30c94aed9b7630d9dda
wpt-pr: 12829
Automatic update from web-platform-testsString_list_directive created
Created a primitive version of function AllowTrustedTypePolicy
"require-trusted-types" changed into "trusted-types" and takes a list of policy names
createPolicy updated to throw when policy name is not allowed
Tests added for policy creation attempt when policy name is on the whitelist and when it isn't
Tests added fot policy creation attempt with no whitelist given
Poked at existing tests to change "require-trusted-types" into "trusted-types"
Removed boolean require_safe_types_ from csp_directive_list
Bug: 739170
Change-Id: Ida0188cf38f8edba8b966b2f708b7a7919d08b29
Reviewed-on: https://chromium-review.googlesource.com/1186325
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Orsolya Bernadett Batiz <orsibatiz@google.com>
Cr-Commit-Position: refs/heads/master@{#588496}
--
wpt-commits: 1de1550e95396f979da97620a289c213acaf55e2
wpt-pr: 12798
Automatic update from web-platform-testsWPT: More refactoring navigation-redirect.https.html
This makes the test more extensible. Preparation for adding tests for
the Clients API and resultingClientId. Specifically, the requestInfos
from the workers and the expectations will have a resultingClientId
in addition to the URL.
Bug: 876223, 778497
Change-Id: Id7c25a77f43f33d40b64ea77c2cf51a0745f57c6
Reviewed-on: https://chromium-review.googlesource.com/1203711
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588479}
--
wpt-commits: d4fb17e0338a3b412af81244d7254cd2b9bc27a0
wpt-pr: 12820
Automatic update from web-platform-tests[WebSocket] Fix cookies/006.html?wss wpt
The websockets/cookies/006.html?wss test didn't work on any modern
browser because you can't set a secure cookie from JavaScript on an
insecure page. See
https://wpt.fyi/results/websockets/cookies/006.html%3Fwss.
Change the expectations to never see the cookie set.
Add a new test, 006.https.html, which runs over https so that the cookie
can be set. Unfortunately, due to mixed content checks, this can't test
the insecure "ws:" scheme, so it still doesn't cover all the cases the
original test intended to.
BUG=803200
Change-Id: I7e280ebc781c693529588a68cd5eef5332b730fa
Reviewed-on: https://chromium-review.googlesource.com/1203495
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588469}
--
wpt-commits: 5ea49ac887f0d4880819d24fe3bc85bc38b96ca7
wpt-pr: 12819
Automatic update from web-platform-tests[cookies] Remove cookies when tests complete (#12817)
Avoid test interactions by removing cookies at the completion of each
test. Use the `add_cleanup` feature of testharness.js to ensure that
this occurs regardless of the passing/failing status of each test.
Persist the existing "setup" logic which defensively removes cookies as
a precaution against still other tests which do not properly restore
global state.
This resolves a known instability caused by
`cookies/prefix/__secure.document-cookie.https.html`. That test sets a
cookie with a "Domain" attribute which
`cookies/prefix/__secure.header.https.html` is not written to remove.
--
wpt-commits: 88e4a9aa658f08de05f6a4d5354c30100c15e688
wpt-pr: 12817
Automatic update from web-platform-testsImplement TextEncoderStream and TextDecoderStream
Add support for streaming encoding and decoding via the
TextEncoderStream and TextDecoderStream.
See design doc
https://docs.google.com/document/d/17goe4jacAYjHHtprfVPSrqDvF_J58u2qirz0HQ58sQ4/edit
Modify transform_stream.cc so it doesn't claim every exception happened
during construction
Remove failing wpt expectations. Add a new test for TextDecoderStream
constructor and property behaviour.
BUG=845427
Change-Id: I538022680ef8e90f5eb2b11fd1775e902e7f25fd
Reviewed-on: https://chromium-review.googlesource.com/1174073
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588443}
--
wpt-commits: fc41987112cd5f0b1198b759ab63e828413a0ee3
wpt-pr: 12467
Automatic update from web-platform-testsHTML: test fieldset content before legend
--
wpt-commits: 7d5c48839d6e9bf65271141e1e4900e63411b23c
wpt-pr: 12810
Automatic update from web-platform-testsLint CSS-COLLIDING-TEST-NAME should treat foo and foo-manual as equivalent (#12813)
--
wpt-commits: 3b610ee654fc7b69fd83e6da3c26f7b39a1131f1
wpt-pr: 12813
Automatic update from web-platform-tests[eme] Ensure license is expired before using it (#8623)
This test generates a license that expires 1s from the current time, calls
update() with it, and then waits for 5s before calling play(). However,
Chrome caches a few frames in advance of play() being called. Depending on
the time granularity, the CDM may see a valid license and decode part of
the media file.
This change delays calling update() for 2s to ensure that the license has
expired, and ensures that the browser can't cache frames to use when play()
is called.
--
wpt-commits: 84097c6b8f84bc0d00c208bf7893cd0e10d654d5
wpt-pr: 8623
Automatic update from web-platform-testsFix missing close bracket in css/css-writing-modes/svg-aliasing-001.html (#12788)
--
wpt-commits: 3a58de991a53a5a358234a8ad4e3d7f8d733d34a
wpt-pr: 12788
Automatic update from web-platform-tests[wptrunner] Parameterize Sauce Connect timeout
Parameterize the maximum delay so that consumers may select an
appropriate value according to their connection and the current
performance of the Sauce Labs service.
--
wpt-commits: 8cc024cd4490e672f16958e0d83155bcc8e56cb1
wpt-pr: 12783
Automatic update from web-platform-tests[Image Capture] Add focusDistance constraint.
This CL adds focusDistance to ImageCapture API.
This was added to the spec in
https://github.com/w3c/mediacapture-image/pull/175
Layout tests and mock tests are updated to support the same.
Support for Android is added.
TEST= run the demo in https://codepen.io/rijuB/pen/NzWpxG
use slider to change focusDistance.
BUG=732807
Intent to Implement and Ship discussions:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/oNxzXaFY9c8
Change-Id: I9b7cbf3c85fd35741a8c7ed229910a996e14ee8f
Reviewed-on: https://chromium-review.googlesource.com/1124839
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#588299}
--
wpt-commits: 0313d9f383d954ef401e79f3b669a5781aa3441a
wpt-pr: 12790
Automatic update from web-platform-tests[PE] Fix LayoutBox Client/Padding/Content boxes with scrollbars (especially vertical-rl)
This CL tries to correct the box model when there are scrollbars,
especially in vertical-rl mode. According to
https://www.w3.org/TR/css-overflow-3/#scrollbar-layout, scrollbars
"should be inserted between the inner border edge and the outer
padding edge".
Changes to the previous code:
- Padding|client box now excludes scrollbars, with the help of
(Top|Left|Bottom|Right)ScrollbarWidth methods which can get the
scrollbar widths in physical directions in various writing modes.
- Content box is now based on the new padding box by excluding the
paddings.
- Layout of contents is now based on the correct box model. In
vertical-rl mode, layout of contents in blocks direction starts
from the inner edge of the new content box which has been properly
adjusted for the scrollbar.
- Now LayoutBox::Location() and Location::PhysicalLocation() in the
initial scroll state are correct in all writing-modes. Previously
when they were incorrect in vertical-rl mode and some flex box
directions, requiring an artificial scroll offset to paint the
content at correct place.
- With the correct padding box, content box, Location(),
PhysicalLocation(), we no longer need the band-aid code to create the
correct painted result.
The changed code is mostly in LegacyLayout code. Some changed code is
in LayoutNG that previously converted correct LayoutNG geometries into
the problematic geometries that were previously expected by
LegacyLayout.
The correct box model is required by blink-gen-property-trees because
we can't band-aid the incorrect results in paint properties after
painting.
Bug: 833167,853945,858843,878809,876266
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_layout_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I41faf1ca0bfb95cb287c72703f08c8bd44e9e752
Reviewed-on: https://chromium-review.googlesource.com/1185901
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588201}
--
wpt-commits: f1c3743c75096e9203bdb5bc040b3c97ef5e184d
wpt-pr: 12745
Automatic update from web-platform-testsAdd observable settings for getDisplayMedia()
This CL adds observable settings to MediaStreamTrack objects returned by
getDisplayMedia() calls. These constrainable properties are set before
the stream is returned based on user choice.
Information about these settings are stored in DisplayMediaInformation
struct. It is set in the low level device selection and then parsed by
UserMediaProcessor before passing it to blink.
Bug: 326740
Change-Id: I81d5f2eb24d2c1a37df0fbe2d34bc469fa575bf1
Reviewed-on: https://chromium-review.googlesource.com/1185875
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Weiyong Yao <braveyao@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588162}
--
wpt-commits: 2b7dace05fc1869398ee24f84fda4c0e4c0455ae
wpt-pr: 12638
