Automatic update from web-platform-tests[css-typed-om] remove duplicate test.
there are duplicate tests. so remove one of them.
Bug: 774887
Change-Id: I040ac68b8d2752ea7f952a0ff615f5352cb23b0e
Reviewed-on: https://chromium-review.googlesource.com/939881
Commit-Queue: Hwanseung Lee <hwanseung@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539568}
wpt-commits: bdee13ee73cbb7036363462c456355e461d5262f
wpt-pr: 9695
wpt-commits: bdee13ee73cbb7036363462c456355e461d5262f
wpt-pr: 9695
Automatic update from web-platform-testsRun script directly and don't source it
--
Fix paths when building CSS testsuite
--
Recommend `git submodule` instead of hg for w3ctestlib/apiclient
--
Fix passing arguments to ./build-css-testsuites.sh
--
Update w3ctestlib submodule
--
Update CSS build system requirements
--
Make it possible to set RUN_JOB globally
wpt-commits: e00868e2cc32b51bcc597400ef4ec1ca0fd5e4a7, 009fd7558acd69310568df2adf4292b9f10914af, 5241f45421bb3455b6b3bc362fa63293eb58ce48, fc544d570321a72c7418d45031db456db37c98be, 6b044b942db61b0f91454f254b1b1847c2d36e29, 11da4202dd2541e2dc2d36a4a3b2e265b4fcc6cc, 1305210bed8f4e3ef811998b219f220511d9a27d
wpt-pr: 9602
wpt-commits: e00868e2cc32b51bcc597400ef4ec1ca0fd5e4a7, 009fd7558acd69310568df2adf4292b9f10914af, 5241f45421bb3455b6b3bc362fa63293eb58ce48, fc544d570321a72c7418d45031db456db37c98be, 6b044b942db61b0f91454f254b1b1847c2d36e29, 11da4202dd2541e2dc2d36a4a3b2e265b4fcc6cc, 1305210bed8f4e3ef811998b219f220511d9a27d
wpt-pr: 9602
Automatic update from web-platform-testsMake the data-url-shared.html test a bit prettier/simpler
This has looked odd since
https://github.com/w3c/web-platform-tests/pull/5075 and can be
simplified anyway.
wpt-commits: e28a4f29f2394547dfbcc82df5f96c5436edb837
wpt-pr: 9691
wpt-commits: e28a4f29f2394547dfbcc82df5f96c5436edb837
wpt-pr: 9691
Automatic update from web-platform-testsCheck if git is a batch file on Windows
In the steps for manifest generation, if git is contained in a batch file, subprocess will not be able to find git and will throw a WindowsError. This change makes it so that if a WindowsError is thrown, it will check if using git.bat works.
wpt-commits: 0503e45c79168576d5672532901a7df0545b05fd
wpt-pr: 9652
wpt-commits: 0503e45c79168576d5672532901a7df0545b05fd
wpt-pr: 9652
Automatic update from web-platform-testsReadableStream piping: Add tests for shutting down when readable becomes errored with preventAbort = true (#9591)
For closing, we had 4 tests for the shutdown behavior, but for erroring we only had two.
Rework the forward error propagation tests, so we now have similar variants:
* Errors must be propagated forward: shutdown must not occur until the final write completes
* Errors must be propagated forward: shutdown must not occur until the final write completes; preventAbort = true
* Errors must be propagated forward: shutdown must not occur until the final write completes; becomes errored after first write
* Errors must be propagated forward: shutdown must not occur until the final write completes; becomes errored after first write; preventAbort = true
wpt-commits: 5154532d4152e2cb8b75cbfbcf1c9e6bb4fe651c
wpt-pr: 9591
wpt-commits: 5154532d4152e2cb8b75cbfbcf1c9e6bb4fe651c
wpt-pr: 9591
Automatic update from web-platform-tests[css-typed-om] Add more property tests.
Add more property tests. Most test failures are because our Blink
implementation for these properties are lagging behind spec. The only
weird one is line-height, which seems to return 'normal' for negative
values even though the spec doesn't say that anywhere.
Bug: 774887
Change-Id: I9d4a6918b5e9b5772230999b18c6eec4934bcf19
Reviewed-on: https://chromium-review.googlesource.com/936821
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539222}
wpt-commits: 9659a35d816ff1b32835a2eccf3e0117dea4e5ce
wpt-pr: 9659
wpt-commits: 9659a35d816ff1b32835a2eccf3e0117dea4e5ce
wpt-pr: 9659
Automatic update from web-platform-testsHTMLMediaElement: set `muted_` when cloning element with muted attribute.
This CL works around the fact that cloning does not call the parser
callbacks and the HTML specifications require the attribute to only
have an effect when the element was created. There is unfortunately
no notification that the element creation from `cloneNode()` happens
so we instead rely on a callback meant for something slightly different.
Bug: 811743
Change-Id: Ib7ac55088b9eaad23f9bce0cfc8366fec6fc5b0d
Reviewed-on: https://chromium-review.googlesource.com/937504
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539207}
wpt-commits: 82efd0226a261a41be569357efa2a65596f1fb75
wpt-pr: 9675
wpt-commits: 82efd0226a261a41be569357efa2a65596f1fb75
wpt-pr: 9675
Automatic update from web-platform-testsMove more chrome webaudio layout tests to WPT
Move the DelayNode, DynamicsCompressorNode, and GainNode tests to
WPT.
Manually verified that Firefox passes these texts, except for the
no-dezipper tests which use suspend() on an offline context.
The tests that weren't moved are Chrome-specific.
Bug: 745778
Change-Id: Iea2d31fd556d51ddcd63e9d139e53f05732261fe
Reviewed-on: https://chromium-review.googlesource.com/922544
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539200}
wpt-commits: 1dd2953e47d12905513d7a295370c3e74bdc6948
wpt-pr: 9654
wpt-commits: 1dd2953e47d12905513d7a295370c3e74bdc6948
wpt-pr: 9654
Automatic update from web-platform-tests[LayoutNG] Need to lay out legacy objects to figure out their inline size.
NG cannot always calculate the correct size of objects that are laid out
by the legacy engine, so just lay them out if we need to know their
size.
The computed CSS width on a table may not end up as its used value, for
instance.
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Iaa327ad21055d6c1af96241b5403193c8b4b5ba3
Reviewed-on: https://chromium-review.googlesource.com/937261
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539201}
wpt-commits: c3e1a513c1d09c2b4544ad05ea3f03ba8483af27
wpt-pr: 9673
wpt-commits: c3e1a513c1d09c2b4544ad05ea3f03ba8483af27
wpt-pr: 9673
Automatic update from web-platform-testsUpdate assumptions test to match HTML spec (#9674)
wpt-commits: 9ff5d62fc664214b86ec8ef4b07aaa8097f7ebed
wpt-pr: 9674
wpt-commits: 9ff5d62fc664214b86ec8ef4b07aaa8097f7ebed
wpt-pr: 9674
Automatic update from web-platform-tests[css-typed-om] Add tests for images related properties.
This patch adds tests for properties taking an <image>. There are some
failing tests due to keywords not implemented in Blink yet.
Bug: 774887
Change-Id: Ie5fa1fa15a16440273517afdd62b078449e615e4
Reviewed-on: https://chromium-review.googlesource.com/928056
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539118}
wpt-commits: eb5edccf4ccdd623f4230bab13805106f9a32fc1
wpt-pr: 9615
wpt-commits: eb5edccf4ccdd623f4230bab13805106f9a32fc1
wpt-pr: 9615
Automatic update from web-platform-tests[css-typed-om] Add property test for font-weight.
font-weight is clamped to [0, 1000], so we have to change the out of
range code to handle upperbounds too.
Test failure because we seem to be rounding the font weight, but the
spec doesn't say we should.
Bug: 774887
Change-Id: I75d283dc32d37e04633133fe420817d02953d4e3
Reviewed-on: https://chromium-review.googlesource.com/936722
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539117}
wpt-commits: 2ddb23d97ca301c2a91d63539bcc1eaa448e5d2c
wpt-pr: 9658
wpt-commits: 2ddb23d97ca301c2a91d63539bcc1eaa448e5d2c
wpt-pr: 9658
Automatic update from web-platform-testsRemove dead code prepare_environment in browser.py (#9653)
This isn't called from anywhere. The DBUS_SESSION_BUS_ADDRESS bits were
added in https://github.com/w3c/web-platform-tests/pull/5893 but was
unused even then. Since then it's been copied around a lot.
wpt-commits: c58e51bef6e114539375fa89e094b20c2056ebe9
wpt-pr: 9653
wpt-commits: c58e51bef6e114539375fa89e094b20c2056ebe9
wpt-pr: 9653
Automatic update from web-platform-tests[USVString] Add a rough test case for navigator.registerProtocolHandler
Although r525634 updated the URL type of registerProtocolHandler from DOMString
to USVString, it didn't add a test case because it was a bit complex. Though
it's still hard to add a test case for it, this CL adds a rough test case for now.
Bug: 790860
Change-Id: Ia688494293274ab2c0aa62f9e33a588ca80d2a82
Reviewed-on: https://chromium-review.googlesource.com/933668
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com>
Cr-Commit-Position: refs/heads/master@{#539114}
wpt-commits: afe0178832b87e03398804b0b99952049b5cc61e
wpt-pr: 9643
wpt-commits: afe0178832b87e03398804b0b99952049b5cc61e
wpt-pr: 9643
Automatic update from web-platform-testsCross-link more of the documentation on writing tests
Fixes https://github.com/w3c/web-platform-tests/issues/4923.
wpt-commits: 58f325b2319ba8e868afff49c61dc8516443fde1
wpt-pr: 9669
wpt-commits: 58f325b2319ba8e868afff49c61dc8516443fde1
wpt-pr: 9669
Automatic update from web-platform-testsAdd tests for the use and lack of the .https file name flag
In https://github.com/w3c/web-platform-tests/pull/8979 it became obvious
that it's easy to have things mostly working without .https working as
intended, and having infrastructure tests for this seems helpful. (I
tried to run all the infrastructure tests first.)
wpt-commits: 0db78b1aec61fff44bb825d43364bd5d7dc9df29
wpt-pr: 9668
wpt-commits: 0db78b1aec61fff44bb825d43364bd5d7dc9df29
wpt-pr: 9668
Automatic update from web-platform-tests[USVString] Apply USVString into Document.origin
The latest spec changed DOMString type of Document.origin with USVString.
- https://dom.spec.whatwg.org/#document
This CL applies USVString type into the Document.origin in order to meet the change.
Bug: 790860
Change-Id: Ibd1fafa28a6e999f7d3085aa7bb4cca0f92d8b2b
Reviewed-on: https://chromium-review.googlesource.com/928005
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539096}
wpt-commits: f63598ecdbe3a6220fc21d6f5d2378b9e1602d47
wpt-pr: 9624
wpt-commits: f63598ecdbe3a6220fc21d6f5d2378b9e1602d47
wpt-pr: 9624
Automatic update from web-platform-testscreateElement()/createElementNS() dictionary argument can be a string
Helps with https://github.com/whatwg/dom/pull/572.
wpt-commits: 2a181b39ebedeb3b2d826fb5f320a7871e0eff08
wpt-pr: 9586
wpt-commits: 2a181b39ebedeb3b2d826fb5f320a7871e0eff08
wpt-pr: 9586
Automatic update from web-platform-tests[css-typed-om] Rejig CSSResourceValue hierarchy.
We implement the new CSSImageValue, which is an opaque object with no
constructor. We also had to change the testsuite.js a bit to test it.
Bug: 545318
Change-Id: I0ae719c5380e01ff9423e0ff0684afe547de1bb0
Reviewed-on: https://chromium-review.googlesource.com/934001
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538730}
wpt-commits: 5ca972e15cfa80277964645d9ee5ccd87a661337
wpt-pr: 9641
wpt-commits: 5ca972e15cfa80277964645d9ee5ccd87a661337
wpt-pr: 9641
Automatic update from web-platform-tests[LayoutNG] The padding box needs to exclude both borders and scrollbars.
We forgot to subtract space taken up by scrollbars. Now that we do, we
also need NGBlockNode::GetScrollbarSizes() to add the horizontal
scrollbar on the correct side. Need to check with the layout object, not
directly with computed style. This matters e.g. if the object in
question is the LayoutView, which always places it on the right hand
side, even if document direction is RTL.
Also fix static block offset in flipped blocks writing mode. We got it
wrong, because we flipped an offset relative to the border edge around
the padding box. That's a regression from
https://chromium-review.googlesource.com/926004
Since I managed to break stuff without any tests regressing, I added a
few to wpt/css/css-flexbox/ (it doesn't really matter which layout model
to test with, as long as the containing block is in legacy layout, so
I just picked flexbox).
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I9527e8bb013b792a6b8ef58b370efe02b071c8bf
Reviewed-on: https://chromium-review.googlesource.com/931502
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538871}
wpt-commits: 0fe9f012a8ee5503b728a379705a6c5286ba1e96
wpt-pr: 9646
wpt-commits: 0fe9f012a8ee5503b728a379705a6c5286ba1e96
wpt-pr: 9646
Automatic update from web-platform-testsUpdate Web Platform Tests for storage APIs in 'data:' contexts
Per https://github.com/w3c/web-platform-tests/pull/4832 remove
WebSQL cases from WPT's workers/data-url*.html since it's not
otherwise tested in WPT, and the test "passes" even if the API is
not present. Also add an addition assertion that indexedDB is
present before blithely checking that using it throws.
WebSQL is not exposed to Workers in Chrome so we don't lose
coverage here - we only "passed" because the API was not present
in these contexts. The webexposed/ tests cover this.
Change-Id: I0aa05ff9e674351a2a49ba0bae8e5a9938b2cf34
Reviewed-on: https://chromium-review.googlesource.com/929602
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538833}
wpt-commits: d116ec3d76ee417df0982c4dde13c1baa846cf42
wpt-pr: 9609
wpt-commits: d116ec3d76ee417df0982c4dde13c1baa846cf42
wpt-pr: 9609
Automatic update from web-platform-testsMake the browser.py documentation more truthful
Not very useful, though...
wpt-commits: 4fda93528ee4eaa1f9164bc99da9cc59e3e33432
wpt-pr: 9649
wpt-commits: 4fda93528ee4eaa1f9164bc99da9cc59e3e33432
wpt-pr: 9649
Automatic update from web-platform-testsUpdate style before computing current animations
This allows CSS animations to be in a proper state for the call.
Bug: 813908
Change-Id: Ibd3870432b0c6fc8cc1766fe5c8abec3263db879
Reviewed-on: https://chromium-review.googlesource.com/927322
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538799}
wpt-commits: 96bff4707999fe178331a9a6818f14703a9ae217
wpt-pr: 9611
wpt-commits: 96bff4707999fe178331a9a6818f14703a9ae217
wpt-pr: 9611
Automatic update from web-platform-testsSwitch external_host to host_ip. (#9258)
When running tests in Firefox we don't require that the hostname is
actually resolvable since we set up some internal DNS overrides. This
means that we don't actually need to have web-platform.test defined in
/etc/hosts. As a consequence when we check the server is responding,
the check will typically fail for Firefox developers if we try to
access by hostname. Previously we made use of a special dance in which
external_host held the ip at the point of the check and was later
replaced by host to actually run tests. But that changed, and instead
we relied on the fact that we (accidentially) didn't actually fail in
the case the servers couldn't be reached by host name. However in some
cases things still failed because local DNS resolved web-patform.test
to some ip address, causing hangs or other badness.
In this patch we simply add a host_ip property to the config, and
connect to that to test the servers are repopnsing rather than the
hostname. We also actually fil if we didn't manage to connect to all
the servers.
wpt-commits: 1ccd3325cc17d53d037cc94335dd20d8d2e54c92
wpt-pr: 9258
wpt-commits: 1ccd3325cc17d53d037cc94335dd20d8d2e54c92
wpt-pr: 9258
Automatic update from web-platform-testsUpdate requests from 2.14.2 to 2.18.4
--
Pin requests to latest version 2.18.4
--
Add pyup configuration file.
We want to only allow updates to specified requirements files, rather than touching
everything under third_party, etc.
wpt-commits: 0989f18782090f10b8861590a0b8089dfb28052a, 1cdf3e435da54d5766bf365ea08c5838525b1d97, 28ceecaaa6f0ff2cae0c586c54a923a1246393c3
wpt-pr: 9588
wpt-commits: 0989f18782090f10b8861590a0b8089dfb28052a, 1cdf3e435da54d5766bf365ea08c5838525b1d97, 28ceecaaa6f0ff2cae0c586c54a923a1246393c3
wpt-pr: 9588
Automatic update from web-platform-testsAdd the "dtmf" attribute on RTCRTPSender
This brings the API into conformance with the spec:
https://w3c.github.io/webrtc-pc/#dom-rtcdtmfsender
The CL also exposes the RTCDTMFToneChange event, which
was previously marked [ NoInterface ].
Bug: 812587
Change-Id: I4122d1e4e336b811de234ed492f0de02dcc7a714
Reviewed-on: https://chromium-review.googlesource.com/926181
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538782}
wpt-commits: 580021b740830fcbdb881da8820c5e147967b1d3
wpt-pr: 9583
wpt-commits: 580021b740830fcbdb881da8820c5e147967b1d3
wpt-pr: 9583
Automatic update from web-platform-testsImplemented cascading of the RequiredCSP through nested contexts
An iframe that is inside another iframe that has as RequiredCSP should
respect that RequiredCSP.
Spec: https://w3c.github.io/webappsec-csp/embedded/#required-csp
Bug: 779031
Change-Id: I9042d63a6d14f48fd3cf1caaccf22c5cd1aa6d7a
Reviewed-on: https://chromium-review.googlesource.com/924064
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538760}
wpt-commits: aa7041bbd31b1a67759161e52ec680e200140e22
wpt-pr: 9557
wpt-commits: aa7041bbd31b1a67759161e52ec680e200140e22
wpt-pr: 9557
Automatic update from web-platform-testsUpdate move-to-fullscreen-iframe-manual.html to match the spec
This test is from https://chromium-review.googlesource.com/776599 and
the explanation seemed to make sense spec-wise. But when matching the
spec more closely this begins to fail, and it seems that per spec
this updated behavior is what would happen.
wpt-commits: db1a703c3785094e38bbf29497157ff4652e04df
wpt-pr: 9299
wpt-commits: db1a703c3785094e38bbf29497157ff4652e04df
wpt-pr: 9299
