Automatic update from web-platform-testsbluetooth: Migrate remaining tests
This change will migrate the remaining tests that have been converted
to the Web Bluetooth Test API at the moment.
BUG=509038
Change-Id: I6b38a9dd413f99caccbc9861d492eec0a25b1b91
Reviewed-on: https://chromium-review.googlesource.com/891653
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538680}
wpt-commits: 99ea9dc824968a32965cf5552069148b60d93d4d
wpt-pr: 9323
wpt-commits: 99ea9dc824968a32965cf5552069148b60d93d4d
wpt-pr: 9323
Automatic update from web-platform-tests[css-typed-om] Add unsupported tests for color properties.
For color properties, we support 'currentcolor' as a CSSKeywordValue,
but any other value (including identifiers like 'red') are not supported
and are converted to base CSSStyleValues.
We add tests for most color related properties. We are failing the
text-emphasis-color one because we haven't unprefixed it yet.
We change the code to make this work.
Bug: 774887
Change-Id: Ide5463b9f67b63568ff32bd34e977faf16964bc1
Reviewed-on: https://chromium-review.googlesource.com/927943
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538668}
wpt-commits: 5496784a17bae2872a9c29a2f7948533218e9d00
wpt-pr: 9614
wpt-commits: 5496784a17bae2872a9c29a2f7948533218e9d00
wpt-pr: 9614
Automatic update from web-platform-testsservice worker: Update WPT test for resource timing
Before this CL, the test assumed that there should be a
PerformanceResourceTiming for fetching 'resources/missing.jpg'.
As the spec says [1], this assumption is not guaranteed. In fact,
Chromium doesn't add PerformanceResourceTiming for resouces which
failed to load. This CL updates the test to check there is a
corresponding PerformanceResourceTiming entry before doing
verifications.
[1] https://w3c.github.io/resource-timing/#resources-included-in-the-performanceresourcetiming-interface
Bug: 782958
Change-Id: I85e75a8dade9f6620d22a54eaf97468f00360023
Reviewed-on: https://chromium-review.googlesource.com/930109
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538648}
wpt-commits: 30c0131604f63247d98aced8f71e756189da7eb2
wpt-pr: 9627
wpt-commits: 30c0131604f63247d98aced8f71e756189da7eb2
wpt-pr: 9627
Automatic update from web-platform-tests[css-typed-om] Give default value for CSSVariableReferenceValue.fallback
The spec gave a default value for CSSVariableReferenceValue.fallback:
372f85caa4
No observable changes to behaviour.
Bug: 814487
Change-Id: Id33f16167c8b8d9eac3fb70ce7e817de659c7465
Reviewed-on: https://chromium-review.googlesource.com/932921
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538623}
wpt-commits: 7bfbc0fa30aad867faa1c6cc748884be76635a08
wpt-pr: 9639
wpt-commits: 7bfbc0fa30aad867faa1c6cc748884be76635a08
wpt-pr: 9639
Automatic update from web-platform-testsAdd 1x1-green.png to WPT media.
This patch adds the 1x1-green.png test image to wpt/media. It seems to
be used quite a lot by other tests too so maybe this is a good place
for it?
Change-Id: Id8a8c0e0c3b0471db273ad2695155addb2cc11fc
Reviewed-on: https://chromium-review.googlesource.com/917441
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538536}
wpt-commits: 54ffc5cc68ba05a3c26379bd51f2390de7bd454f
wpt-pr: 9504
wpt-commits: 54ffc5cc68ba05a3c26379bd51f2390de7bd454f
wpt-pr: 9504
--HG--
rename : testing/web-platform/tests/css/css-typed-om/resources/1x1-green.png => testing/web-platform/tests/media/1x1-green.png
Automatic update from web-platform-tests[SPv175] Don't crash on circular filter reference containing foreignObject or svg-in-svg
This is a workaround for the crash bugs. The root cause is tracked
in crbug.com/814815.
Bug: 813446, 813411, 814815
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ied370eb2b1f0ffd4424c9c397ea1c899914bdbb0
Reviewed-on: https://chromium-review.googlesource.com/931922
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538527}
wpt-commits: 7ed02d443a806ab9fd27fbb15138cab57410c651
wpt-pr: 9637
wpt-commits: 7ed02d443a806ab9fd27fbb15138cab57410c651
wpt-pr: 9637
Automatic update from web-platform-testsMoved and .name return the address of the document (#9559)
wpt-commits: a83f934cf3c350cac147029659806f5acdc76f2f
wpt-pr: 9559
wpt-commits: a83f934cf3c350cac147029659806f5acdc76f2f
wpt-pr: 9559
Automatic update from web-platform-tests[css-typed-om] Update WPT IDL test and clean up implementation IDL.
This patch updates the WPT IDL test to the current spec.
We also clean up the implementation IDL to match the spec.
Bug: 812915
Change-Id: Id2ca308832344e824b0e7b7eaa6198dc6d7c7e03
Reviewed-on: https://chromium-review.googlesource.com/930502
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538371}
wpt-commits: 7e6dcfb79fc94b2093ae45ed54167b7b106b7f43
wpt-pr: 9622
wpt-commits: 7e6dcfb79fc94b2093ae45ed54167b7b106b7f43
wpt-pr: 9622
Automatic update from web-platform-tests[css-typed-om] Make sure implementation IDL matches spec IDL.
This patch updates our IDL to match that of the spec. We found two
issues in the process:
- StylePropertyMap.get should return (undefined or CSSStyleValue),
but IDL doesn't provide that yet. The spec uses "any" as a workaround
but we'll return (null or CSSStyleValue) for now (null vs undefined).
We'll change the code once IDL gives us something for this.
- Iteration should always return a sequence of CSSStyleValue, whereas
they used to return either CSSStyleValue or sequence of CSSStyleValues
depending on whether the property was list valued or not.
We change the code to fix this.
We deleted the inlineStylePropertyMap_iteration.html LayoutTest
as it is already covered by WPT.
We also update the WPT test expectations to match the spec.
Bug: 812915
Change-Id: Id2f9fbba4398c9ecfd63ea3f8e1aad0b3a0b499f
Reviewed-on: https://chromium-review.googlesource.com/925981
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538367}
wpt-commits: 53a527f9fe52a3707b93a4458e2fb7205ee19683
wpt-pr: 9581
wpt-commits: 53a527f9fe52a3707b93a4458e2fb7205ee19683
wpt-pr: 9581
Automatic update from web-platform-testsAdd srcset/imgsizes support for <link rel=preload> in LinkLoader
This patch teaches LinkLoader to recognize srcset / imgsizes attributes
when preloading images.
This feature is behind the Experimental Web Platform feature flag. Also
note that the attribute name is temporary and may change as the spec
discussion progresses.
Bug: 813452
Change-Id: I82770edd7a99ec328c3748f192f98cf9df0af274
Reviewed-on: https://chromium-review.googlesource.com/927930
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538365}
wpt-commits: fc9b65044ce69f4edb7ded4cf9be83ac2d71fb24
wpt-pr: 9595
wpt-commits: fc9b65044ce69f4edb7ded4cf9be83ac2d71fb24
wpt-pr: 9595
Automatic update from web-platform-testsRevert "Port another set of sticky tests to JS rather than reftests"
This reverts commit 913109149534a732bdb5461d0ba2759f5d2f50f4.
Reason for revert:
Multiple failures on Linux, for example:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty/39500https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20%28dbg%29/9251
Original change's description:
> Port another set of sticky tests to JS rather than reftests
>
> Change-Id: Idf6dd882d2d50b1ec349f245d76717553ee266b3
> Reviewed-on: https://chromium-review.googlesource.com/882002
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532966}
TBR=flackr@chromium.org,smcgruer@chromium.org
Change-Id: I7a773131066157e0d4216d7fa7c228bd8bff2021
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/893536
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533000}
wpt-commits: bfe08e0b1b1cb016e78d41cdf792db33b7f58070
wpt-pr: 9625
wpt-commits: bfe08e0b1b1cb016e78d41cdf792db33b7f58070
wpt-pr: 9625
Automatic update from web-platform-tests[LayoutNG] The available space on a line may be affected by text-indent.
Corrected a DCHECK and added a test that used to crash (but otherwise
pass).
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I139fda3ce912c9138fc055ca7d55d568d5017092
Reviewed-on: https://chromium-review.googlesource.com/928653
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538346}
wpt-commits: 48a72dd95fcf0352f30297cd5d8293331aabed7e
wpt-pr: 9607
wpt-commits: 48a72dd95fcf0352f30297cd5d8293331aabed7e
wpt-pr: 9607
Automatic update from web-platform-testsUse red images for service worker multipart-image wpt
external/wpt/service-workers/service-worker/multipart-image.https.html
checks the image data of multipart image when loading succeeds. The
check was flaky because we used different colors for each part
(green and red) and the content of the image data depends on which
part of the multipart image is currently shown. Since it's difficult
to detect which part is currently shown, we use the same color (red)
for each part to avoid the flakiness.
Bug: 813775
Change-Id: Iaafb4c02b2b72831951b5f6c244eea0b62153cd5
Reviewed-on: https://chromium-review.googlesource.com/930062
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538339}
wpt-commits: 6fea5b1b40cf678fdbca7e9cf3a132256fe9f8fd
wpt-pr: 9620
wpt-commits: 6fea5b1b40cf678fdbca7e9cf3a132256fe9f8fd
wpt-pr: 9620
Automatic update from web-platform-testsbluetooth: Migrate service is removed tests
This change moves the service is removed tests into wpt/.
BUG=509038
Change-Id: I3472ee5dca6ea3706b4f8383790fa3a1f2a81c76
Reviewed-on: https://chromium-review.googlesource.com/904730
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538284}
wpt-commits: 981f9153417351495150354d81676bfab5cd7ac5
wpt-pr: 9464
wpt-commits: 981f9153417351495150354d81676bfab5cd7ac5
wpt-pr: 9464
Automatic update from web-platform-tests[css-typed-om] Add per-property test for 'opacity'.
This patch adds tests for opacity, which only takes a <number> and whose
computed value is clamped to [0, 1]. This is the <number> property so
we had to add to the test harness.
Bug: 545318
Change-Id: I5689843188811c8c14c062a60deb0a8c580de3d9
Reviewed-on: https://chromium-review.googlesource.com/927745
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538269}
wpt-commits: 9b97da2b2f50e97d7809f56002fade93358fd41c
wpt-pr: 9594
wpt-commits: 9b97da2b2f50e97d7809f56002fade93358fd41c
wpt-pr: 9594
Automatic update from web-platform-tests[css-layout-api] Populate styleMap and give to layout function.
This adds both style-invalidation for the LayoutCustom object, as well
as giving the populated StylePropertyMapReadOnly to the layout()
function.
ComputedStyle::DiffNeedsFullLayout now needs a Document in order to look
up the DocumentLayoutDefinition, to see which properties need to checked
for change.
Bug: 726125
Change-Id: Ie462cb624ba413c796131433ea4eae9bb9f3ec13
Reviewed-on: https://chromium-review.googlesource.com/926906
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538268}
wpt-commits: 6aeb9ea2a3874d39418e7ea15778a719ec0d482d
wpt-pr: 9590
wpt-commits: 6aeb9ea2a3874d39418e7ea15778a719ec0d482d
wpt-pr: 9590
Automatic update from web-platform-testswebdriver: make test_handle_prompt_accept consistent with other similar tests (#9612)
Other webdriver tests that test the same thing for other commands all test
for accepting a `prompt()` dialog to look for either the empty string ("")
or undefined as the value returned by the method. This makes the
fullscreen tests consistent with those others.
wpt-commits: e92532746b7615dcccdfa060937a87664816b1db
wpt-pr: 9612
wpt-commits: e92532746b7615dcccdfa060937a87664816b1db
wpt-pr: 9612
Automatic update from web-platform-testswebdriver: remove ES6 constructs from pages (#9600)
Internet Explorer doesn't support ES6 constructs like fat arrow functions.
So that the WebDriver tests can be executed against IE, the pages loaded
in the browser by the tests shouldn't include such constructs.
wpt-commits: d6dc97a217ddb16ed70a57326f7c6236faef13a0
wpt-pr: 9600
wpt-commits: d6dc97a217ddb16ed70a57326f7c6236faef13a0
wpt-pr: 9600
Automatic update from web-platform-testswebdriver: add property name for self-referential array object (#9603)
To create a full object for use with Internet Explorer, the object literal
should contain a property name for the self-referential array object
added as a property value.
wpt-commits: 0d68b017755cc6e8890391f213f4376e0a52502c
wpt-pr: 9603
wpt-commits: 0d68b017755cc6e8890391f213f4376e0a52502c
wpt-pr: 9603
Automatic update from web-platform-testswebdriver: add additional enabled <option> element in test page (#9601)
Clicking on a disabled <option> element should not allow it to become
selected. However, if the disabled <option> is the only child element of
the <select> element, it may be marked as selected by the user agent. This
commit allows the test to attempt to call elementClick on a disabled
<option> without it being selected.
wpt-commits: cf1569d41abb8dd17fcb70cdff37ea4486a2b281
wpt-pr: 9601
wpt-commits: cf1569d41abb8dd17fcb70cdff37ea4486a2b281
wpt-pr: 9601
Automatic update from web-platform-testswebdriver: fix some issues in fullscreen tests (#9575)
The test test_handle_prompt_accept seems to think that the
Fullscreen Window command returns the window title, which is
not the case. Remove wrong assertions. The return payload is
checked by a different test case.
The test test_handle_prompt_missing_value has a typo in a
global variable lookup. This throws a JS exception at runtime.
Tests that use is_fullscreen fail when run in WebKit because
WebKit does not yet conform to the Fullscreen API and its existing
properties and methods are prefixed. Add a fallback and a note
with the WebKit bug that blocks removing this fallback.
wpt-commits: a98c69d9778bdf736cfc1665fd22bc31df76248c
wpt-pr: 9575
wpt-commits: a98c69d9778bdf736cfc1665fd22bc31df76248c
wpt-pr: 9575
Automatic update from web-platform-testsPort another set of sticky tests to JS rather than reftests
Change-Id: Idf6dd882d2d50b1ec349f245d76717553ee266b3
Reviewed-on: https://chromium-review.googlesource.com/882002
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532966}
wpt-commits: c67d9e1d65aaf3e852dcd9b00b5feb40e80f36b7
wpt-pr: 9523
wpt-commits: c67d9e1d65aaf3e852dcd9b00b5feb40e80f36b7
wpt-pr: 9523
Automatic update from web-platform-testsEnsure we always run against the latest version of Firefox. (#9537)
Previously we were downloading a version by looking for the first
match of the supplied regexp on the download page. That doesn't work
well in general and we need to look through the listings for the
version with the highest number.
wpt-commits: 9d8895d75af32e8f3a3a558d0dede40881705c78
wpt-pr: 9537
wpt-commits: 9d8895d75af32e8f3a3a558d0dede40881705c78
wpt-pr: 9537
Automatic update from web-platform-testsUpdate reftests in manifest when reftests become non-reftests (#9598)
In https://github.com/w3c/web-platform-tests/pull/9523 some tests were
converted from reftests to testharness, but the incremental manifest
update mechanism doesn't handle this case. This appears to be the cause
of the mysterious Travis failures on that PR.
The added test failed without the code changes.
wpt-commits: 86195076e37a960ff44fa86edc54699455f3a4aa
wpt-pr: 9598
wpt-commits: 86195076e37a960ff44fa86edc54699455f3a4aa
wpt-pr: 9598
Automatic update from web-platform-testscc Add https://streams.spec.whatwg.org/demos tests
When JavaScript-syntax checking for `script`-element contents was
recently added to the HTML checker, it broke the build of the Streams
spec due to some documents in https://streams.spec.whatwg.org/demos/
using some newer JavaScript syntax that the Rhino parser (which the HTML
checker relies on) doesn’t understand yet.
So to ensure those cases get handled correctly, some refinements were
made to the HTML checker and the Rhino fork it uses. The documents are
added here to ensure no regressions occur.
wpt-commits: 46c5f2bbb079c919f47e5842ab01e4da1a23b0da
wpt-pr: 9596
wpt-commits: 46c5f2bbb079c919f47e5842ab01e4da1a23b0da
wpt-pr: 9596
Automatic update from web-platform-tests[css-typed-om] Remove StylePropertyMap.getProperties().
This patch removes StylePropertyMap.getProperties() as it
is the same as StylePropertyMap.keys().
Bug: 545318
Change-Id: Ib31c70478306f415c4c184e1b2148f35759f58c4
Reviewed-on: https://chromium-review.googlesource.com/925883
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538033}
wpt-commits: eb5d88a3f712661c75c0f1ba051c06e97d43de1a
wpt-pr: 9580
wpt-commits: eb5d88a3f712661c75c0f1ba051c06e97d43de1a
wpt-pr: 9580
Automatic update from web-platform-tests[LayoutNG] Use containing block size correctly for abspos.
UpdateOutOfFlowBlockLayout() needs to deal with both the actual
containing block size, as specified by CSS (i.e. the padding box size),
and the border-box size of the object that is the containing block of an
absolutely positioned descendant.
Some light cleanup. We always need the border sizes, so just calculate
them once, unconditionally. Also, there seems no need for a special path
for grid/flex, so I removed it.
Some tests start to pass. All but one are still expected to fail in legacy.
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I85462d76aa9fa3d0105bf079e59f7c2a7a70f117
Reviewed-on: https://chromium-review.googlesource.com/926004
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537918}
wpt-commits: 58462b6f92aab3eea03ad1ea70923855889ed1e2
wpt-pr: 9589
wpt-commits: 58462b6f92aab3eea03ad1ea70923855889ed1e2
wpt-pr: 9589
Automatic update from web-platform-testsFix WebAudio WPT tests that timeout.
- AudioParam IDL test:
Actually add the IDL to the test. Also removed unused helpers.js.
- MediaElementAudioSourceNode
Fix error because the expected result is mono, so only has one channel.
However, this still fails on bots because there's no audio hardware to
drive the online context.
Bug: 626703
Test: the-audioparam-interface/idl-test.html
Change-Id: I987ad1219da1b6b6ef677f2923416634fa281d5f
Reviewed-on: https://chromium-review.googlesource.com/920261
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537856}
wpt-commits: 0d5ca044187f3e1122661048e84a54e736296198
wpt-pr: 9548
wpt-commits: 0d5ca044187f3e1122661048e84a54e736296198
wpt-pr: 9548
Automatic update from web-platform-testsReadableStream: test piping and queued writes
When the readable stream becomes closed after the first write,
all queued writes should complete before the pipe operation
becomes completed.
This tests the fix for this behavior in the Streams reference
implementation in whatwg/streams#884.
wpt-commits: 4c74a92846442ebb277342c3afe663a2c89955d4
wpt-pr: 9573
wpt-commits: 4c74a92846442ebb277342c3afe663a2c89955d4
wpt-pr: 9573
Automatic update from web-platform-testsUpdate supported font format specifiers
While we do support variations, our format specifier support was not
updated yet. Move all of that to FontCustomPlatformData and add a WPT
test to cover common supported format specifiers.
Test: external/wpt/css/css-fonts/format-specifiers-variations.html
Bug: 804466
Change-Id: I06d7af65cf74e13cec49dc279efb8ffc2b56dda9
Reviewed-on: https://chromium-review.googlesource.com/926007
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537799}
wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c
wpt-pr: 9585
wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c
wpt-pr: 9585
Automatic update from web-platform-testsFix #8954: update wptrunner requirements
Note this just uses the current stable release of all dependencies
rather than trying to find what the minimum required actually is.
--
Pin wptrunner dependencies
Given it's an application, we should just define the environment we
expect it to run in. This should stop #8954 from regressing, given it
also means we'll be testing against the only possible set of versions
of our dependencies.
wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb
wpt-pr: 9587
wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb
wpt-pr: 9587
Automatic update from web-platform-testsOOR-CORS: Port WebCORSPreflightResultCacheItem to network service
This patch reimplements WebCORSPreflightResultCacheItem equivalent
in network service, and share the implementation between the network
service and Blink. The next patch will replace whole
WebCORSPreflightResultCache, and this is the preparation to make
the next patch small.
Bug: 803766
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ifa06967830465236dbe198908062e1952095e55b
Reviewed-on: https://chromium-review.googlesource.com/915543
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537769}
wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53
wpt-pr: 9539
wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53
wpt-pr: 9539
Automatic update from web-platform-testsDelete StylePropertyMap.update()
This is as there is a bug on the spec highlighting the lack of
usefulness of the function: https://github.com/w3c/css-houdini-drafts/issues/656
Bug: 812912
Change-Id: If0b47a4bfa268f55f63e5c80168971164dc63199
Reviewed-on: https://chromium-review.googlesource.com/923501
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537697}
wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025
wpt-pr: 9554
wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025
wpt-pr: 9554
Automatic update from web-platform-tests[css-typed-om] Fix crash involving negative length perspectives.
We were crashing because converting CSSPerspective(-1px) to a CSSValue
returns nullptr. The correct behaviour should be to convert it as
CSSPerspective(calc(-1px)).
Bug: 812620
Change-Id: I5ee70d4fb5eed064bcdad67391c3eb84531144d6
Reviewed-on: https://chromium-review.googlesource.com/924742
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537690}
wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d
wpt-pr: 9567
wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d
wpt-pr: 9567
Automatic update from web-platform-tests[css-typed-om] Handle out-of-range values correctly.
Currently, when we set width to something like -1, we would get an
invalid value for width. According to the spec [1], we should be
wrapping the invalid value in a calc.
This patch wraps invalid values in calc, and changes the test harness
to allow us to test this.
Bug: 545318
Change-Id: I71769e1bc69164c9b7dcf0d2c54ca06b623b5d9e
Reviewed-on: https://chromium-review.googlesource.com/923603
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537685}
wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20
wpt-pr: 9568
wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20
wpt-pr: 9568
Automatic update from web-platform-testsFix #7142: Change manifest update process
Earlier, interrupting the manifest-update could end up
causing errors due to the non-atomicity of the process.
Used tempfile to ensure that the file is written correctly.
wpt-commits: 38612167f54c475836c122013756e92b9a8859cc
wpt-pr: 9564
wpt-commits: 38612167f54c475836c122013756e92b9a8859cc
wpt-pr: 9564
Automatic update from web-platform-testsFix wpt/beacon/headers/header-content-type.html slowness
This CL uses ResourceTiming API to speed up the test cases while
avoiding flakiness.
Bug: 779965
Change-Id: I40dc2fae470df296c87c12e432fc7fc7644cc40a
Reviewed-on: https://chromium-review.googlesource.com/923625
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537664}
wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102
wpt-pr: 9569
wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102
wpt-pr: 9569
Automatic update from web-platform-testsStreams: Tests for abuse of RSBYOBRequest (#9558)
In https://github.com/whatwg/streams/pull/870 it was made impossible to
directly construct a ReadableStreamBYOBRequest. Prior to that it was
possible to violate the state invariants of ReadableByteStreamController
by constructing then using a BYOBRequest directly. Add tests that verify
that it is not possible to construct a ReadableStreamBYOBRequest
directly.
Also add tests that it isn't possible to violate the invariants of
ReadableByteStreamController by re-using a BYOBRequest object.
Also add a test that it isn't possible to keep a BYOBRequest object
valid while releasing the reader lock, as this would also be a way to
violate ReadableByteStreamController's invariants.
Fixeswhatwg/streams#870
wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db
wpt-pr: 9558
wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db
wpt-pr: 9558
Automatic update from web-platform-testsRefactor tests for sandbox iframes controlled by service worker
This patch is to split sandboxed-iframe-fetch-event.https.html into small
chunks. Each promise_test has smaller number of assertions, so that now we can
see the results for each situation.
Bug: 771815
Change-Id: I75cdd67f92bbb07d6b538b209e1f0819752c3bc8
Reviewed-on: https://chromium-review.googlesource.com/923901
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537606}
wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989
wpt-pr: 9556
wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989
wpt-pr: 9556
Automatic update from web-platform-testsStop reusing MemoryCache entries for requests with a different source origin.
ResourceFetcher/ResourceLoader now saves the result of the CORS check on
the Resource object. Though the result of the CORS check varies
depending on the source origin, reusing an existing resource fetched by
a different source origin is allowed by mistake.
This patch introduces a logic to prevent MemoryCache entries from being
reused for requests with a different source (requestor) origin by saving
the source origin on the Resource object and comparing that with the new
source origin in Resource::CanReuse(), so that the result of the CORS
check is reused only when the source origin is the same.
An alternative possibly-better approach is to isolate MemoryCache for
different origins by changing the cache identifier to take into account
the source origin of requests. However, to keep the patch small and fix
the issue quickly, this patch just prevents reuse.
Bug: 799477, 809350
Change-Id: Ib96c9e728abe969a53f3d80519118a83392067b4
Reviewed-on: https://chromium-review.googlesource.com/897040
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537580}
wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3
wpt-pr: 9536
wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3
wpt-pr: 9536
Automatic update from web-platform-testsSet WasFetchedViaServiceWorker for multipart image response
When creating a ResourceResponse from another ResourceResponse,
we need to copy WasFetchedViaServiceWorker and
ResponseTypeViaServiceWorker.
Bug: 737648
Change-Id: I9405738221ef5232e235f9fc400f204b7b558596
Reviewed-on: https://chromium-review.googlesource.com/907012
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537579}
wpt-commits: 75c962d7c542f3a6c6e43bcf18a4bf67a16f86cf
wpt-pr: 9492
wpt-commits: 75c962d7c542f3a6c6e43bcf18a4bf67a16f86cf
wpt-pr: 9492
Automatic update from web-platform-testsReadableStream: Add a test that all queued writes complete on error (#5636)
When a pipe is errored, all currently queued writes should complete
before abort() is called on the underlying sink.
The tests the fix to this behaviour in the Streams reference
implementation in whatwg/streams#884.
wpt-commits: ee7ca4fb8371000d2429a99002d1ad71275d5cde
wpt-pr: 5636
wpt-commits: ee7ca4fb8371000d2429a99002d1ad71275d5cde
wpt-pr: 5636
Automatic update from web-platform-testsFix selection{Start,End} test
Likely due to a copy and paste error, one of the tests that was
meant to cover both selectionStart and selectionEnd only covered
the former. Fix so that it covers both, as it should have from the
start.
wpt-commits: 08dd5d8de9c165badabf9f18b5be21a561d8213a
wpt-pr: 9563
wpt-commits: 08dd5d8de9c165badabf9f18b5be21a561d8213a
wpt-pr: 9563
Automatic update from web-platform-tests[css-layout-api] Implement the guts of the javascript layout runner.
This implements the hooks from the LayoutCustom object into a web
developer defined layout class.
See: https://drafts.css-houdini.org/css-layout-api/#invoke-a-layout-callback
Currently the only useful thing this does to allow the web developer to
return an "auto" block-size, e.g.
registerLayout('foo', class {
*intrinsicSizes() {}
*layout() {
return { autoBlockSize: Math.random() * 100; } // FUN!
}
});
The engine calculates the inline-size, and adjusts the block-size for the
web developer. This is a simplification on the current API as spec'd but
we'll see what the HoudiniTF thinks of this approach.
The other large behaviour change is appropriate "fallback" handling when
something goes wrong. See "fallback" tests.
Bug: 726125
Change-Id: I08cd2e439f4321bd534a4e3f7222fbdb898e1785
Reviewed-on: https://chromium-review.googlesource.com/917423
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537371}
wpt-commits: 1a2e430c6fd35c111ead0d5a0e9afbe874e7c1a2
wpt-pr: 9509
wpt-commits: 1a2e430c6fd35c111ead0d5a0e9afbe874e7c1a2
wpt-pr: 9509
Automatic update from web-platform-testsCorrect integration with Sauce Labs service (#9484)
A recently merged patch centralized configuration values which defined
the domain names available during test execution [1]. That patch was
based on a mistaken assumption regarding the location of that value and
the stage of the test execution at which it would be available.
(Specifically: the value is not present in the environment configuration
object when the "environment extras" are initialized.) This interfered
with the initialization of the "environment" for the Sauce Labs service,
making it impossible to run the tests there.
Defer the retrieval of the environment configuration object to the time
that object's context manager is activated. Update the call sites to
provide the environment configuration at this moment. Also update the
signature of the context manager for the `FontInstaller` "environment
extra" to accept this second parameter.
[1] https://github.com/w3c/web-platform-tests/pull/8614
wpt-commits: e56563d2b1e8bd225bf4c8b4682cbd12beeae1a7
wpt-pr: 9484
wpt-commits: e56563d2b1e8bd225bf4c8b4682cbd12beeae1a7
wpt-pr: 9484
Automatic update from web-platform-testswptrunner: Fix regression in config, interpreter (#9480)
Prior to the application of this patch, the configuration property named
`host` was required to expand the templated JSON file maintained within
the WPT CLI. By removing the property from some browser definitions
without updating that template, commit 1b4f253 introduced failures when
using the `run` sub-command with the effected browsers.
Refactor the logic for generating the configuration to use an in-memory
representation (instead of a file-based template) and conditionally
extend this object with the `host` option for browsers which specify it.
Document the rationale for the browser which requires this
functionality.
wpt-commits: cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56
wpt-pr: 9480
wpt-commits: cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56
wpt-pr: 9480
Automatic update from web-platform-testsFix timeouts in WPT AudioParam tests
Replace the tests that are using ScriptProcessor and online contexts
with an offline context and verify all the output values instead of
just one.
This change exposed a couple of issues:
- setTargetAtTime wasn't actually testing setTargetAtTime because a
linearRampToValueAtTime event was called at the same time,
effectively replacing the setTargetAtTime event
- linearRampToValue and exponentialRampToValue tests expose bugs in
Chrome's implementation of these when the event is scheduled in
the past, and there is no preceding event.
Bug: 812285, 626703
Change-Id: Iad3f54dd4373411431c019de44d4c3bad07587ff
Reviewed-on: https://chromium-review.googlesource.com/919151
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537311}
wpt-commits: 81ada4212ece1e2f5c6cc560d6b2f45593679e93
wpt-pr: 9524
wpt-commits: 81ada4212ece1e2f5c6cc560d6b2f45593679e93
wpt-pr: 9524
Automatic update from web-platform-tests[LayoutNG] Don't add zero-width floats to the exclusion space.
The only thing such floats should affect is the block position of
subsequent floats (float rule §5 [1] and clearance). They should not
affect the inline position or inline size of subsequent floats or new
formatting contexts.
The spec isn't actually clear here, although the browsers agree on the
above. Submitted https://github.com/w3c/csswg-drafts/issues/2312
[1] https://www.w3.org/TR/CSS22/visuren.html#float-position
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Ia9e724c8a58fcb017f86f26bdf90394f09414f4e
Reviewed-on: https://chromium-review.googlesource.com/919065
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537274}
wpt-commits: ae06fa4ce5d170f7f34e979b014315e318344ec4
wpt-pr: 9538
wpt-commits: ae06fa4ce5d170f7f34e979b014315e318344ec4
wpt-pr: 9538
Automatic update from web-platform-testsservice worker: Disallow interception for EMBED and OBJECT requests.
This matches the service worker specification and Firefox.
This change itself is probably not enough to skip all EMBED/OBJECT
requests, as some requests get initiated by PepperURLLoaderHost or
MimeHandlerViewContainer.
In implementor concerns:
https://w3c.github.io/ServiceWorker/#implementer-concerns
"Plug-ins should not load via service workers. As plug-ins may get their
security origins from their own urls, the embedding service worker cannot
handle it. For this reason, the Handle Fetch algorithm makes the
potential-navigation-or-subresource request (whose context is either <embed> or
<object>) immediately fallback to the network without dispatching fetch event."
In Handle Fetch:
https://w3c.github.io/ServiceWorker/#handle-fetch
"If request is a potential-navigation-or-subresource request, then:
Return null."
R=kinuko, yhirano
Bug: 771933
Change-Id: Ia04ae8dec8c968de6a73dca088aa88a67b21718a
Reviewed-on: https://chromium-review.googlesource.com/923445
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537245}
wpt-commits: e7607dad61b547e88d1f06a67b1514a3242600ec
wpt-pr: 9555
wpt-commits: e7607dad61b547e88d1f06a67b1514a3242600ec
wpt-pr: 9555
Automatic update from web-platform-tests[css-typed-om] Make StylePropertyMap.set work with calcs.
Currently StylePropertyMap.set doesn't actually work with calcs.
The current way to check if something is, say, a <length> is to
check its CSSStyleValue::Type. However, this doesn't return
the right value for CSSMathValues, whose types may be quite
complicated.
The correct way is to use the CSSNumericValue matching algorthms:
CSSNumericValue::MatchesLength, which also takes into account
CSSMathValues and percent hints.
This patch changes the following to make this work:
- Removed base types from CSSStyleValue::StyleValueType. A base type
like "length" is not really a CSSStyleValue type.
- Removed unused StyleValueTypeToString.
- Changed "Percent" to "Percentage" in CSSProperties.json5 as that's
the correct term.
- Changed make_cssom_types to use the matching algorithms from
CSSNumericValue.
Bug: 545318
Change-Id: I16aa71a4873e9992749f0f52ba641671d109170e
Reviewed-on: https://chromium-review.googlesource.com/901002
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537206}
wpt-commits: b52a7a29208647f209f06ac2e6321987023c196c
wpt-pr: 9535
wpt-commits: b52a7a29208647f209f06ac2e6321987023c196c
wpt-pr: 9535
Automatic update from web-platform-testsAdd initial test set for Accessible Name and Description Computation 1.1 (#9540)
Note that many of the tests are currently named with a number. Those
tests were taken from the original (1.0) test suite created by the
PFWG, and the file names are being preserved to facilitate comparison
of results.
wpt-commits: 2b4cdad36bd267e39565ebaab5982b9b4c482e53
wpt-pr: 9540
wpt-commits: 2b4cdad36bd267e39565ebaab5982b9b4c482e53
wpt-pr: 9540
Automatic update from web-platform-testsAdd tests for the breaking of a multicolumn across columns, including backgrounds and column rules. (#9527)
The *-nobackground-* tests pass in Firefox and Chrome, and the others
pass in Chrome and fail in Firefox due to what I (as a Gecko
implementor) consider to be a Firefox bug. I haven't yet tested other
engines. (Though -nobackground-003 fails in Firefox due to a different
bug, and multicol-breaking-002 doesn't trigger the background-related
Firefox bug.)
Given the level of ambiguity in the multicol spec, I suspect these tests
probably test some things that aren't formally specified. However, I
think that's probably OK for now. One issue that I know of that they
depend on the spec for is w3c/csswg-drafts#2309.
wpt-commits: d04c0d50dbbf7752c27957005a5a659701b781ad
wpt-pr: 9527
wpt-commits: d04c0d50dbbf7752c27957005a5a659701b781ad
wpt-pr: 9527
Automatic update from web-platform-testsReftest for handling important when there is an animation.
This tests https://drafts.csswg.org/css-cascade/#importance
wpt-commits: 5ee47da05ffc366a887788ccdc3f7a0673c35953
wpt-pr: 8689
wpt-commits: 5ee47da05ffc366a887788ccdc3f7a0673c35953
wpt-pr: 8689
Automatic update from web-platform-tests[USVString] Apply USVString into RTCDataChannel.send
Latest spec changed DOMString type of send with USVString.
- https://w3c.github.io/webrtc-pc/#dom-rtcdatachannel
This CL applies USVString type into the RTCDataCchannel.send according to the spec.
Bug: 790860
Change-Id: I3d2e3fef8e6a8cc8ca94a8ae18c2ccb7dcc48016
Reviewed-on: https://chromium-review.googlesource.com/917741
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Commit-Queue: Tommi <tommi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537015}
wpt-commits: 1a3951e267e61077ca566e9872c9abeb229d5751
wpt-pr: 9530
wpt-commits: 1a3951e267e61077ca566e9872c9abeb229d5751
wpt-pr: 9530
Automatic update from web-platform-tests[LayoutNG] Allow zero-width layout opportunities.
Zero-width floats or in-flow block-level objects that establish a new formatting
context may fit beside preceding floats even if there's zero inline space left.
With this change, a couple of tests start passing, but coverage seems a
bit low, so I added a few new ones.
Had to rebaseline fast/text/word-break.html because a zero-width line
may now fit beside a float that takes up all available inline
space. There was a <br clear=all> in the test that used to insert the
line below such a float. We're now compatible with the others (and our
old selves).
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Iaf394b7039545eea235b2841457f1662e5890ba9
Reviewed-on: https://chromium-review.googlesource.com/916262
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537000}
wpt-commits: e2b2513a9ab764bcec7ccf616a35835d13020e32
wpt-pr: 9503
wpt-commits: e2b2513a9ab764bcec7ccf616a35835d13020e32
wpt-pr: 9503
Automatic update from web-platform-testsUpdating Server creation for localhost (#9202)
In my last change, I missed this line of code. Adding the host parameter and removing the base_path param.
wpt-commits: 09ca41d71aab5d5640804b34e5165f291259f112
wpt-pr: 9202
wpt-commits: 09ca41d71aab5d5640804b34e5165f291259f112
wpt-pr: 9202
Automatic update from web-platform-testsMake WPT webrtc/simplecall.html pass
The test was failing because passing a null ("end of candidates")
candidate to addIceCandidate is not permitted.
Spec link:
https://www.w3.org/TR/webrtc/#dom-rtcpeerconnection-addicecandidatehttps://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addicecandidate
Bug: none
Change-Id: I1f22d27393a482a882ebe9735488d8cb723b6e75
Reviewed-on: https://chromium-review.googlesource.com/918662
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536977}
wpt-commits: 49d8cd27466bcd293f86a5758f21fcd23a97f196
wpt-pr: 9516
wpt-commits: 49d8cd27466bcd293f86a5758f21fcd23a97f196
wpt-pr: 9516
Automatic update from web-platform-tests[css-typed-om] Move inline style map layout tests to WPT.
We used to have some inline style map layout tests for a subset of
properties. This patch moves them to WPT using the new test harness.
Properties added:
- white-space
- vertical-align
- visibility
- z-index
Bug: 774887
Change-Id: Icce056c4d7f56eed3da05834b1c561fddec53a15
Reviewed-on: https://chromium-review.googlesource.com/918203
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536966}
wpt-commits: e4730a5e002aadca9605485aec9ccb4c122f15de
wpt-pr: 9514
wpt-commits: e4730a5e002aadca9605485aec9ccb4c122f15de
wpt-pr: 9514
Automatic update from web-platform-testsCSS2 tests were only correct if the default font has two weights. (#9533)
font-weight-rule 005 and 007 both made the incorrect
assumption that there were no weights lighter than 400
or greater than 700 in the default font. Added new
references for them which don't depend on that.
wpt-commits: 30c492f9078d50bff86b4459e78d31cc0d7bf47b
wpt-pr: 9533
wpt-commits: 30c492f9078d50bff86b4459e78d31cc0d7bf47b
wpt-pr: 9533
Automatic update from web-platform-testsAdd test for wrappable content that has flex:none (#9518)
Add test for wrappable content that has flex:none
See https://bugzilla.mozilla.org/show_bug.cgi?id=1374540; per spec, the
flex:none content should be allowed its full content width. This
currently works in Chrome, Edge, Safari, and Opera.
wpt-commits: a02389e2cc84576b8aa35bff9658f6db39003ed8
wpt-pr: 9518
wpt-commits: a02389e2cc84576b8aa35bff9658f6db39003ed8
wpt-pr: 9518
Automatic update from web-platform-testsMerge pull request #9397 from faceless2/bfo-css-fonts-3-fontfeature
Added new testcases to test font-variant precedence rules
wpt-commits: 840362217deb3f9b82fe18a619d0bf21ddc55781
wpt-pr: 9397
wpt-commits: 840362217deb3f9b82fe18a619d0bf21ddc55781
wpt-pr: 9397
Automatic update from web-platform-testsCheck that fetch request signal following works correctly
This test already tests integration, so this is just an extra check.
Follows https://github.com/whatwg/fetch/pull/670.
wpt-commits: e151f898bfde2bfb518206008a911577be8a5a68
wpt-pr: 9515
wpt-commits: e151f898bfde2bfb518206008a911577be8a5a68
wpt-pr: 9515
Automatic update from web-platform-tests[css-typed-om] Move inline style map layout tests to WPT.
We used to have some inline style map layout tests for a subset of
properties. This patch moves them to WPT using the new test harness.
Properties added:
- position
- padding-{top,bottom,left,right}
- text-align
- text-decoration-style
Bug: 774887
Change-Id: I9fc9d6d425b1a5ce0c71f8d918bc5893c74c4e89
Reviewed-on: https://chromium-review.googlesource.com/917927
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536698}
wpt-commits: 9e98749811573be88146eaeac56732d445f769fd
wpt-pr: 9513
wpt-commits: 9e98749811573be88146eaeac56732d445f769fd
wpt-pr: 9513
Automatic update from web-platform-testsSetting "" as <track> 'src' should fail the first time
When setting a track .src to "", we would resolve the URL to a null URL,
which matched the default initialized HTMLTrackElement::url_, meaning
that readyState was not advanced and no 'error' event fired in this
case.
Extend the "url == url_" check with a check for readyState differing from
'none'. Also rewrite HTMLTrackElement::getReadyState to avoid using
EnsureTrack().
Bug: 811713
Change-Id: Icd190492639c53e09a7e018202b69ac6e919a94c
Reviewed-on: https://chromium-review.googlesource.com/916004
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: srirama chandra sekhar <srirama.m@samsung.com>
Cr-Commit-Position: refs/heads/master@{#536685}
wpt-commits: 7bdac4aedb60223226e5941b7cc8ebadfcc9885b
wpt-pr: 9498
wpt-commits: 7bdac4aedb60223226e5941b7cc8ebadfcc9885b
wpt-pr: 9498
Automatic update from web-platform-tests[css-typed-om] Move inline style map layout tests to WPT.
We used to have some inline style map layout tests for a subset of
properties. This patch moves them to WPT using the new test harness.
Fixed some bugs involving properties not given the correct metadata
(e.g. border-style should not take an <image>).
Transform is failing tests because it should compute to as specified
but it's computing to 'none' (will fix this later).
TODO in follow up patches:
- Test list-valued properties properly.
- Add more test examples to <position> and <image>.
Bug: 774887
Change-Id: I93f20a457e2220329b661787c7d557ee28b1f62d
Reviewed-on: https://chromium-review.googlesource.com/917921
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536658}
wpt-commits: 783faf5a3f8803a1a1f4f30345f67de333a6d72c
wpt-pr: 9511
wpt-commits: 783faf5a3f8803a1a1f4f30345f67de333a6d72c
wpt-pr: 9511
Automatic update from web-platform-testsFetch API: Don't DCHECK on a 302 response with a Location header with empty value.
Blink was failing a DCHECK when it expected a redirect to be taken because
the request mode was 'follow' and the response had a redirect status code
and Location header. However, Chrome's //net considers a Location header
with an empty value to be the same as no Location header at all. See the
comments on bug 810288 about net::HttpResponseHeaders::IsRedirect().
WPT tests are added. The spec is unclear (https://github.com/whatwg/url/issues/373)
but seems to either say to fail with network error or enter a loop of self-redirects
that will eventually hit the redirect limit and fail with network error.
Chrome currently fails this test because it treats the Location as
as non-existent, i.e., not a redirect response.
Bug: 810288,707185
Change-Id: Iaca93976aaa697380b1542ab45d63c318f5050b0
Reviewed-on: https://chromium-review.googlesource.com/910753
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536644}
wpt-commits: e75788501733a0801eec374c19f8cdfbccd9c09d
wpt-pr: 9453
wpt-commits: e75788501733a0801eec374c19f8cdfbccd9c09d
wpt-pr: 9453
Automatic update from web-platform-tests[custom-elements] Add HTML serialization tests
This is for https://github.com/whatwg/html/pull/3444
wpt-commits: d0114efdde520f9aa003ce42c85ef134f01ad691
wpt-pr: 9508
wpt-commits: d0114efdde520f9aa003ce42c85ef134f01ad691
wpt-pr: 9508
Automatic update from web-platform-tests[css-typed-om] Refactor the per-property test harness.
This patch refactors the per-property test harness quite
a bit to deal with property specific behaviour:
- We allow tests to override the expectation/asserts
for specified and computed values. So it means that a
property might compute 'auto' to '0px' and we can easily
assert that by passing a callback to 'computed'.
- We moved margin-top to margin and test all the margin
properties (except the margin shorthand).
- We made margin properties work by setting the correct
metadata in the CSSProperties.json5.
- We removed unitless zero tests. They don't seem to
be required by the spec.
Bug: 774887
Change-Id: I08605ac6af01576ff9f6c878c2ca9e280c9948e1
Reviewed-on: https://chromium-review.googlesource.com/915884
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536603}
wpt-commits: 5479ebec26b46fa4ecf02698863c3ea1d64c3126
wpt-pr: 9507
wpt-commits: 5479ebec26b46fa4ecf02698863c3ea1d64c3126
wpt-pr: 9507
Automatic update from web-platform-tests[custom-elements] Some fixes for "is" attribute behavior changes
This is for https://github.com/whatwg/dom/pull/566.
- document.createElement() and createElementNS() don't add "is" content
attribute.
- cloneNode() should clone custom elements even if they have no "is"
content attributes or have "is" content attribute inconsistent with
"is value."
wpt-commits: 1e4fe87a7f01c0b5c614c8f601ffa68b4a00662a
wpt-pr: 9505
wpt-commits: 1e4fe87a7f01c0b5c614c8f601ffa68b4a00662a
wpt-pr: 9505
Automatic update from web-platform-tests[Picture-in-Picture] Add PictureInPictureWindow width and height stubs
This introduces PictureInPictureWindow interface with |width| and
|height| attributes. |onresize| event will follow in an upcoming CL.
|width| and |height| simply return fake values, respectively 500 and
300, for now as we don't have any resize events coming from the backend
yet. They are reset to 0 though when PictureInPictureWindow state is
closed.
Bug: 806249
Change-Id: I5e0f0875a53b7f659bc3469e562d3db5e075f31d
Reviewed-on: https://chromium-review.googlesource.com/899347
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: apacible <apacible@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536520}
wpt-commits: e9ffe0be14f695ad5fb0aa104bbddbcc88712f56
wpt-pr: 9370
wpt-commits: e9ffe0be14f695ad5fb0aa104bbddbcc88712f56
wpt-pr: 9370
Automatic update from web-platform-testsCorrect serialization of background-color (#9499)
According to https://drafts.csswg.org/css-color/#resolving-color-values, transparent should serialize to "rgba(0, 0, 0, 0)", and named colors should serialize to their equivalent value in rgb notation. Change the expectations for 3 background tests in order to match this part of the spec.
wpt-commits: 43deb07215d283d63e2bdca51d6268eba43bbe81
wpt-pr: 9499
wpt-commits: 43deb07215d283d63e2bdca51d6268eba43bbe81
wpt-pr: 9499
Automatic update from web-platform-testsHandle ::slotted in ComputeLinkMatchType.
We skipped the selector list for ::slotted looking for :visited and
:link pseudo classes and ended up applying such rules with both :visited
and :link style.
Bug: 808392
Change-Id: I85956902f3ca9cea01c96ef5c56ccf7f0ee23671
Reviewed-on: https://chromium-review.googlesource.com/904903
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536328}
wpt-commits: c6b11a5cbcd934c4394f7451529dc18269400ff1
wpt-pr: 9413
wpt-commits: c6b11a5cbcd934c4394f7451529dc18269400ff1
wpt-pr: 9413
Automatic update from web-platform-testscustom-elements: document.importNode() for customized built-in elements should work
importNode() implementation should pass "is" value to "create an
element" algorithm.
WPT: Add a new test for importNode().
Bug: 807871
Change-Id: Id60c5577b5899aeac66b819986c34a28978e24d9
Reviewed-on: https://chromium-review.googlesource.com/915744
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536311}
wpt-commits: 79f402f76e5b78f0fae93dbff7c4ddc5cd382e04
wpt-pr: 9494
wpt-commits: 79f402f76e5b78f0fae93dbff7c4ddc5cd382e04
wpt-pr: 9494
Automatic update from web-platform-testscustom-elements: Support cloneNode() for customized built-in elements
Element::CloneElementWithoutAttributesAndChildren() should use "create
an element" algorithm with |is| value.
Note that a change in SVGScriptElement.cpp isn't necessary because
Custom Elements V1 doesn't support SVG elements. This CL updates
SVGScriptElement.cpp for consistency and clean code.
WPT: Add cloneNode() tests to custom-elements/builtin-coverage.html.
Bug: 807871
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Iaa7d2781b916e2459ee244540d619cfffcf42427
Reviewed-on: https://chromium-review.googlesource.com/915401
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536297}
wpt-commits: 57780dfd0c0e917a9196974e2d528ac1c705136b
wpt-pr: 9491
wpt-commits: 57780dfd0c0e917a9196974e2d528ac1c705136b
wpt-pr: 9491
Automatic update from web-platform-testsIgnore order when parsing inset and color for box-shadow
According to the spec [1], box-shadow should allow the inset keyword and
a color in any order. Our implementation allowed only 2 out of the 4
possible orders; fix our parsing to match the spec.
[1]: https://drafts.csswg.org/css-backgrounds/#typedef-shadow
Bug: 811083
Change-Id: I54c3d15c177702624994c45044b446fd82fc9d98
Reviewed-on: https://chromium-review.googlesource.com/911994
Commit-Queue: Chris Nardi <cnardi@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536270}
wpt-commits: 9c1c6c3d5513b9b7d46a2c57c0950875ff6dd389
wpt-pr: 9474
wpt-commits: 9c1c6c3d5513b9b7d46a2c57c0950875ff6dd389
wpt-pr: 9474
Automatic update from web-platform-testsAsync Cookies: Fix globals in idlharness test
Globals (Window, ServiceWorkerGlobalScope, etc) get special bindings
treatment for methods/properties and IDL tests for features need to
declare these types correctly for correct results. Fix the SW test for
the new cookie store API by marking the global with the [Global]
extended attribute; this reveals that our implementation passes all
the bindings test cases.
Bug: 729800
Change-Id: I87747ed2af8d932342e24c9400524d88c9df73a7
Reviewed-on: https://chromium-review.googlesource.com/914568
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536189}
wpt-commits: b0e401ab8394d8117db2bce6095dedf0150c66d6
wpt-pr: 9486
wpt-commits: b0e401ab8394d8117db2bce6095dedf0150c66d6
wpt-pr: 9486
Automatic update from web-platform-testsUpstream IIRFilterNode tests to WPT
Needed to include a copy of biquad-filters.js, so we have two copies
of this now.
Bug: 745778
Test: webaudio/IIRFilter moved to WPT
Change-Id: I7d4bf534b6502c7d5d38bfb490adf71862427a69
Reviewed-on: https://chromium-review.googlesource.com/909306
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536125}
wpt-commits: 0eb48551ba11bf4a2c66b856bf5da95ba0fefbd5
wpt-pr: 9441
wpt-commits: 0eb48551ba11bf4a2c66b856bf5da95ba0fefbd5
wpt-pr: 9441
Automatic update from web-platform-testsImprove RTCRtpSender.replaceTrack tests' Firefox compatibility
The current test relies on addTrack(track) which is not the
API tested. Using addTrack(track, stream) works in Firefox
as well as Chrome.
BUG=790007
Change-Id: I098101cd6556620c42b4f51df98ef54b0a8ad1f7
Reviewed-on: https://chromium-review.googlesource.com/912289
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536063}
wpt-commits: e02ec4ac5b399ee2fe41b7628b58f305f7d66558
wpt-pr: 9479
wpt-commits: e02ec4ac5b399ee2fe41b7628b58f305f7d66558
wpt-pr: 9479
Automatic update from web-platform-tests[LayoutNG] Improve min/max calculation wrt. floats.
The presence of floats complicate min/max intrinsic inline size
calculation. They affect lines and child blocks in the same block
formatting context. Therefore, when calculating min/max sizes of a
child, we need to pass along information about floats adjacent to the
current "virtual" block position.
This change actually makes NG slightly "better" than legacy Blink
layout, Edge and Firefox. This may be an issue for compatibility. It
should be fairly easy to "dumb down" the machinery to be compatible with
the others, though, if this should become an issue. Two tests regressed
because of this. Reported bug 810370. This change also caused
grid-item-margins-not-collapse-expected.html to make room for the floats to
fit beside each other, so I modified it. Also removed bogus "margin"
attributes.
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I59730d7333fa7699a42ab93d2c4674c267d834aa
Reviewed-on: https://chromium-review.googlesource.com/908753
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536044}
wpt-commits: 84696c45e08c43b0e26888ac0a4823769c067228
wpt-pr: 9442
wpt-commits: 84696c45e08c43b0e26888ac0a4823769c067228
wpt-pr: 9442
Automatic update from web-platform-testsTest document.body and document.bgColor when root is not <html> (#9231)
See https://github.com/whatwg/html/issues/3403
wpt-commits: 7996359a0b41061c4c6e7fa2db8ef18b65587820
wpt-pr: 9231
wpt-commits: 7996359a0b41061c4c6e7fa2db8ef18b65587820
wpt-pr: 9231
Automatic update from web-platform-tests[css-typed-om] Implement CSSTransformComponent.toMatrix().
This patch implements CSSTransformComponent.toMatrix(), which was
previously implemented as AsMatrix() but just not webexposed. We also
split up the tests since it makes more sense.
Bug: 807877
Change-Id: Icee742fdde033d63cea85a27250e91a71ad67e2a
Reviewed-on: https://chromium-review.googlesource.com/910529
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536022}
wpt-commits: 8d2483fc61ae071d6aa9126d0417814a22dd4134
wpt-pr: 9475
wpt-commits: 8d2483fc61ae071d6aa9126d0417814a22dd4134
wpt-pr: 9475
Automatic update from web-platform-tests[css-typed-om] Test that styleMap.set rejects invalid values.
Currently, our per-property tests only test that styleMap.set accept
valid values. This patch refactors the per-property tests a bit to
also test that we reject invalid values.
Bug: 774887
Change-Id: I41b5c4c1a6dfe6e766ff37fdc1b1f890dfb81aac
Reviewed-on: https://chromium-review.googlesource.com/905523
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536021}
wpt-commits: 9d904638217b0c43b0e741829f1998d38a61337d
wpt-pr: 9417
wpt-commits: 9d904638217b0c43b0e741829f1998d38a61337d
wpt-pr: 9417
Automatic update from web-platform-testsCSS translate: serialize % as percent for computed values
The CSS translate property no longer resolves percentages
in getComputedStyle results.
CSS WG Resolution:
RESOLVED: % values of translate are serialized as percent for
computed values. Add note making the behavior explicit.
https://github.com/w3c/csswg-drafts/issues/2124
BUG=811027
Change-Id: I6f9b60c285d1eccc2e13ff0e806794df5cce5151
Reviewed-on: https://chromium-review.googlesource.com/912052
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#536010}
wpt-commits: 9b23a0cbf6476d3f1d0b25b9bda8e5249725b00b
wpt-pr: 9469
wpt-commits: 9b23a0cbf6476d3f1d0b25b9bda8e5249725b00b
wpt-pr: 9469
