Automatic update from web-platform-testsDOM: test composed/composedPath via IDL (#9968)
--
wpt-commits: a4c4257d4c6df3000aad94b0c3ae1afc7c5aa5c6
wpt-pr: 9968
Automatic update from web-platform-testsAvoid FutureWarnings in test_sourcefile.py. (#10518)
These lines of code triggered the following warning:
> FutureWarning: The behavior of this method will change in future versions.
> Use specific 'len(elem)' or 'elem is not None' test instead.
--
wpt-commits: 4a7f047bde7fef6a753abcfc6393770db2c6569a
wpt-pr: 10518
Automatic update from web-platform-testsURL.createObjectURL should not work with MediaStream (#10515)
Change the one existing test to no longer rely on it (and clearly mark it as manual) and add an entry to historical.html for it.
--
wpt-commits: b4e3ffbc3251172b79a9a82fa8e4ff290cc61449
wpt-pr: 10515
Automatic update from web-platform-testsTest vertical tab for base64
Apparently Rust's base64 crate strips this, so it would be good to test. Safari is also an outlier here.
--
wpt-commits: 412b4039cce45779eb2a294a26ce7151fd79c0d0
wpt-pr: 10441
Automatic update from web-platform-testsInstall Ahem for Safari on Sauce (#10491)
This just gets the latest master version of the font; we could change
things to get the version for the current revision, but it isn't
necessarily worth the extra complexity given how rarely this changes.
--
wpt-commits: 60308987fb8a877ee2d3ff32946e040d3efab495
wpt-pr: 10491
Automatic update from web-platform-tests[wptrunner] Install Ahem in Sauce Labs Windows VM (#10499)
--
wpt-commits: f76bdbfac3b5a115c11b07d81a03830d4618a1aa
wpt-pr: 10499
Automatic update from web-platform-testsFix wpt/css/CSS2/floats-clear/clear-on-parent-with-margins-no-clearance.html
The test was incorrect, which is why it failed in legacy layout. It
passed in LayoutNG because of a bug there.
Add an (invisible) top border on the outer DIV to prevent clearance on
the child. Otherwise the outer DIV and the child with 'clear' would have
adjacent margins, which in turn would enable the child with 'clear' to
pull the float along with itself, which in turn would guarantee
clearance, which is precisely what this test wanted to avoid.
Still passes in LayoutNG.
Change-Id: I6b36d8196b93720453d6e398509705d2cf32f8e4
Reviewed-on: https://chromium-review.googlesource.com/1014975
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551443}
--
wpt-commits: 4a0df34066201cfe683293de6e93cf093dde9e6d
wpt-pr: 10504
Automatic update from web-platform-testsFixed config.json not being used in TestEnvironment (#10494)
Added a check in the TestEnvironment load_config so it overrides the
default config when present.
Closes https://github.com/w3c/web-platform-tests/issues/8181
--
wpt-commits: 8824132b3278f9ad126764689464e515d9a62473
wpt-pr: 10494
Automatic update from web-platform-testsPaymentHandler: Not allow to call operation if event is not trusted
Related spec change:
https://github.com/w3c/payment-handler/pull/294
Bug: 833530
Change-Id: I65d0e01bb5b6bfdd44925b90ba98837161cc136b
Reviewed-on: https://chromium-review.googlesource.com/1013664
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#551238}
--
wpt-commits: e08f2142aa8e98034966994966e02fff3747bdf8
wpt-pr: 10483
Automatic update from web-platform-testsApply automatic pull for AudioWorkletNode with zero output
Spec: https://webaudio.github.io/web-audio-api/#rendering-loop (Step 9.5)
The AudioWorkletNode with zero output must be pulled by the renderer.
The actual output will be ignored just like AnalyserNode.
Bug: 831245
Test: LayoutTests/external/wpt/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-automatic-pull.https.html
Change-Id: If9bd27d6c4bfeecdcd2dd4c8445459afd8593e85
Reviewed-on: https://chromium-review.googlesource.com/1014388
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551210}
--
wpt-commits: 7eed33a59decf3541af0b014968008e2c55a9f92
wpt-pr: 10496
Automatic update from web-platform-testsUpdate mozprofile from 0.29 to 1.0.0 (#10453)
--
wpt-commits: 25b6727b41d8ad70dcf8da8d8057e2b85f7cc2ce
wpt-pr: 10453
The PNG data generated in this test creates a 100x100 image with opaque green
pixels in the left 50px and fully transparent pixels in the right 49px. The 1px
vertical strip of pixels at pixel column 50 are green pixels with .66 alpha.
The test was failing because it supplied a shape-image-threshold of .25, and
thus was floating by 51px instead of the intended 50px. This change modifies
the test to use a shape-image-threshold of .7, generating the intended 50px
float area.
MozReview-Commit-ID: GJtym0p95yk
--HG--
extra : rebase_source : f6388475db46a5ced29cf401ce12ae9c28cb81f3
The test shape-outside-circle-027.html has two issues that prevent it from
matching the reference image. For that test to pass, the text must be floated
right by 75 pixels. The two issues are:
1) The circle is defined as 35% of 170 pixels, which calculates to 59.5px.
Since the shape-margin is 15px, this makes the total offset less than the
target of 75px.
2) The circle is offset upwards by 10 pixels, which introduces a slight angle
between the block start of the text and the center of the circle. The
cosine of this small angle is slightly less than 1, which reduces the
offset by some amount.
The changes made here specify the circle radius in whole pixels, and move the
center of the circle such that it is between the block start and block end of
the floated text, ensuring that the full width of the circle + shape-margin
will be used for calculating the float area.
MozReview-Commit-ID: JQ9Mc3GU4tW
--HG--
extra : rebase_source : 18af61015feb06f7fa0b1884dbfd97f927238f8d
https://www.w3.org/TR/css-shapes-1/#funcdef-ellipse states that the
grammar for ellipse is:
ellipse() = ellipse( [<shape-radius>{2}]? [at <position>]? )
This permits either 0 or 2 shape-radius tokens, but not 1. These two tests
use 1 shape-radius token and do not parse correctly.
https://www.w3.org/TR/css-shapes-1/#typedef-shape-radius states that omitted
shape-radius values default to closest-side. This change updates these two
tests to add the closest-side value for the missing shape-radius tokens.
MozReview-Commit-ID: 9UKxJel1b50
--HG--
extra : rebase_source : 2688982811417fe91fea2ba9c202de7a822c290c
https://www.w3.org/TR/CSS2/visudet.html#propdef-line-height specifies that
line-height is given an initial value of normal, which is defined:
Tells user agents to set the used value to a "reasonable" value based on the
font of the element. The value has the same meaning as <number>. We recommend
a used value for 'normal' between 1.0 to 1.2. The computed value is 'normal'.
These tests are designed to work correctly if and only if the line-height
is 1. This change specifies line-height: 1 explicitly.
MozReview-Commit-ID: 3Ueassok0f
--HG--
extra : rebase_source : a6036fa620a67e6e48c795da963f9dd2835beebc
The test added in this patch fails without the corresponding code changes
(specifically the second gGetComputedTimingTests test fails the comparison of
the 'easing' member).
MozReview-Commit-ID: 9eyXruVrPuN
--HG--
extra : rebase_source : 927f55c0670bf770e03d38eb876202efbb700c1e
Running wpt occasionally failed due to an issue starting the ws[s]
servers. This turns out to be a deadlock caused by a logging lock
being inherited into the child process, sometimes in a locked
state. As a workaround, after spawning the subprocess, we reload the
logging module in order to clear any existing lock. This is pretty
much a hack, but it's the fastest path to a solution to a critical issue.
Automatic update from web-platform-testsFetch: align about:blank handling with the standard
See 72fc2e787b.
Closes https://github.com/whatwg/xhr/issues/194.
--
wpt-commits: fa62ac066402b280c37623ee9ec45489939781fc
wpt-pr: 10421
Automatic update from web-platform-testsEnsure cloneNode() does not preserve the prototype
Closes https://github.com/whatwg/dom/issues/565.
--
wpt-commits: 691673d4de5105fab16f3b1a1d8523a5e9699fee
wpt-pr: 9987
Automatic update from web-platform-testsImprove handling of harness-level errors in wptrunner (#10444)
Split the internal handling of errors during a test into two cases;
INTERNAL-ERROR that is produced if there's an exception in the harness
and ERROR that is for exceptions reported by the test. Both are still
reported as ERROR to the user, but in the INTERNAL-ERROR case the
runner is always restarted, just like EXTERNAL-TIMEOUT, since we
assume that the internal state is compromised somehow.
--
wpt-commits: 6736e3f46bc6a110e6e550711208e492f1630eba
wpt-pr: 10444
Automatic update from web-platform-testsCSS: Remove support for position values with 3 parts
Intent:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/oBKMVCOX1sY/BLsXXiukAgAJ
BUG=804187
Change-Id: I94e79b2b426250c521d0ebae1492571fde078f31
Reviewed-on: https://chromium-review.googlesource.com/1013459
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550915}
--
wpt-commits: ff4cf69b8f1d705039d71ceef94dee04e74b35c9
wpt-pr: 10469
Automatic update from web-platform-testsReland "Web Animations: Fix bugs in procedure to process a keyframes argument"
This is a reland of 0ade0386aa4168b48234bc7f33d30a62140b95ea
Original change's description:
> Web Animations: Fix bugs in procedure to process a keyframes argument
>
> There were three minor bugs left in the implementation:
>
> - We threw on lists-in-custom-iterators instead of just ignoring them.
> - We returned all properties on the keyframe rather than just those
> defined on the keyframe itself (e.g. we would include prototype
> properties, against spec).
> - We didn't access the properties in ascending unicode order.
>
> Bug: 827573
> Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88
> Reviewed-on: https://chromium-review.googlesource.com/989261
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#550641}
Bug: 827573
Change-Id: I6c49fa6ca36db16ecddfb520e0964bd231565a0b
Reviewed-on: https://chromium-review.googlesource.com/1012897
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550895}
--
wpt-commits: da5837af9586234669a556c65fab521130688225
wpt-pr: 10465
Automatic update from web-platform-testsReland 2: Use PostTask to schedule cross-process postMessage forwarding.
Changes from first reland attempt at https://crrev.com/c/1011287:
- fix an additional source of flakiness in ChromeOS login tests
Changes from original attempt at https://crrev.com/c/999182:
- fix flakiness in two additional ChromeOS login tests
- fix CSP WPT tests to not depend on ordering between iframe's onload
and postMessage - see https://crbug.com/832319.
Previously, we sent the IPC to forward a cross-process postMessage
immediately. This caused a behavioral difference from the
same-process case where the postMessage is always scheduled. Namely,
in a scenario like this:
frame.postMessage(...);
doSomethingThatSendsIPCsToFrame(frame);
the IPCs from JS following the postMessage would've been ordered
incorrectly, causing |frame| to see their side effects after the
postMessage dispatch in the cross-process case, whereas they would be
seen before the postMessage dispatch in the same-process case. One
example of this is frame.focus(), and another is a frame element
onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after
a postMessage dispatched from an inline script while the frame was
still loading.
To resolve these ordering concerns, this CL changes cross-process
postMessage to do a PostTask on the sender side before sending the
message to the browser process. This improves the current state of
the world, but does not yet achieve a perfect match for the IPC
ordering in the same-process case - see discussion on the bug.
Bug: 828529
Tbr: dcheng@chromium.org
Change-Id: If2cc6591db31471adff0d84ec0b689905e21cdf1
Reviewed-on: https://chromium-review.googlesource.com/999182
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/master@{#550284}
Reviewed-on: https://chromium-review.googlesource.com/1011287
Cr-Original-Commit-Position: refs/heads/master@{#550621}
Reviewed-on: https://chromium-review.googlesource.com/1012472
Cr-Commit-Position: refs/heads/master@{#550769}
--
wpt-commits: c53d084cc57749bc666e42aaceeb34daa42539c7
wpt-pr: 10467
Automatic update from web-platform-testsRevert "Web Animations: Fix bugs in procedure to process a keyframes argument"
This reverts commit 0ade0386aa4168b48234bc7f33d30a62140b95ea.
Reason for revert:
Unexpected Failures:
* bindings/sequence-type.html
* custom-elements/spec/define-element.html
* external/wpt/custom-elements/CustomElementRegistry.html
on
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Mac10.11%20%28dbg%29/https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20%28dbg%29/
Speculatively reverting this to see if it's the cause.
Original change's description:
> Web Animations: Fix bugs in procedure to process a keyframes argument
>
> There were three minor bugs left in the implementation:
>
> - We threw on lists-in-custom-iterators instead of just ignoring them.
> - We returned all properties on the keyframe rather than just those
> defined on the keyframe itself (e.g. we would include prototype
> properties, against spec).
> - We didn't access the properties in ascending unicode order.
>
> Bug: 827573
> Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88
> Reviewed-on: https://chromium-review.googlesource.com/989261
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#550641}
TBR=flackr@chromium.org,yukishiino@chromium.org,jbroman@chromium.org,haraken@chromium.org,smcgruer@chromium.org
Change-Id: I5e8dc0c67599492bd6e90fca4a034e29e334ef88
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 827573
Reviewed-on: https://chromium-review.googlesource.com/1012857
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550721}
--
wpt-commits: cb845c5ab5e3c718f6de85ec6ac285770b9b394f
wpt-pr: 10464
Automatic update from web-platform-testsTest that requestMediaKeySystemAccess sets label (#8508)
On Edge, navigator.requestMediaKeySystemAccess ignores the value passed along to the label configuration field. This test exposes that bug.
See https://goo.gl/6SgCRb
--
wpt-commits: e6cffaa6d307ec6ef08102aad9c7a4a1df5b7d53
wpt-pr: 8508
Automatic update from web-platform-testsRevert "Reland: Use PostTask to schedule cross-process postMessage forwarding."
This reverts commit 7c3d1d13f940e88ef6706fd8b5c257a81d340ed9.
Reason for revert: WebviewLoginTest.Basic is still flaky on linux-chromeos-rel
https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6886https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6887
Original change's description:
> Reland: Use PostTask to schedule cross-process postMessage forwarding.
>
> Changes from original attempt at https://crrev.com/c/999182:
> - fix flakiness in two additional ChromeOS login tests
> - fix CSP WPT tests to not depend on ordering between iframe's onload
> and postMessage - see https://crbug.com/832319.
>
> Previously, we sent the IPC to forward a cross-process postMessage
> immediately. This caused a behavioral difference from the
> same-process case where the postMessage is always scheduled. Namely,
> in a scenario like this:
>
> frame.postMessage(...);
> doSomethingThatSendsIPCsToFrame(frame);
>
> the IPCs from JS following the postMessage would've been ordered
> incorrectly, causing |frame| to see their side effects after the
> postMessage dispatch in the cross-process case, whereas they would be
> seen before the postMessage dispatch in the same-process case. One
> example of this is frame.focus(), and another is a frame element
> onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after
> a postMessage dispatched from an inline script while the frame was
> still loading.
>
> To resolve these ordering concerns, this CL changes cross-process
> postMessage to do a PostTask on the sender side before sending the
> message to the browser process. This improves the current state of
> the world, but does not yet achieve a perfect match for the IPC
> ordering in the same-process case - see discussion on the bug.
>
> Bug: 828529
> Change-Id: I62a627c501526d09900be4f5bd2c899acf4d1e07
> Reviewed-on: https://chromium-review.googlesource.com/999182
> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
> Cr-Original-Commit-Position: refs/heads/master@{#550284}
> Reviewed-on: https://chromium-review.googlesource.com/1011287
> Cr-Commit-Position: refs/heads/master@{#550621}
TBR=xiyuan@chromium.org,dcheng@chromium.org,alexmos@chromium.org
Change-Id: Ic0637a6038bed6e5334a26e1934bee81faad3b9e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 828529
Reviewed-on: https://chromium-review.googlesource.com/1012138
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550649}
--
wpt-commits: 6ad1b51de7dce0d45d08cc0f47a92a7b1fed69d2
wpt-pr: 10463
Automatic update from web-platform-testsWeb Animations: Fix bugs in procedure to process a keyframes argument
There were three minor bugs left in the implementation:
- We threw on lists-in-custom-iterators instead of just ignoring them.
- We returned all properties on the keyframe rather than just those
defined on the keyframe itself (e.g. we would include prototype
properties, against spec).
- We didn't access the properties in ascending unicode order.
Bug: 827573
Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88
Reviewed-on: https://chromium-review.googlesource.com/989261
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550641}
--
wpt-commits: 2707869d65f3a4d5a1f2ab1d44920b19695a7cde
wpt-pr: 10399
Automatic update from web-platform-testsMerge pull request #10462 from ewilligers/background-serialization-variety
Accept variation in serialization of 'background'
--
wpt-commits: 1e5a5fefe15c4fcc1a3267daf1d75598f736c82f
wpt-pr: 10462
Automatic update from web-platform-testsReland: Use PostTask to schedule cross-process postMessage forwarding.
Changes from original attempt at https://crrev.com/c/999182:
- fix flakiness in two additional ChromeOS login tests
- fix CSP WPT tests to not depend on ordering between iframe's onload
and postMessage - see https://crbug.com/832319.
Previously, we sent the IPC to forward a cross-process postMessage
immediately. This caused a behavioral difference from the
same-process case where the postMessage is always scheduled. Namely,
in a scenario like this:
frame.postMessage(...);
doSomethingThatSendsIPCsToFrame(frame);
the IPCs from JS following the postMessage would've been ordered
incorrectly, causing |frame| to see their side effects after the
postMessage dispatch in the cross-process case, whereas they would be
seen before the postMessage dispatch in the same-process case. One
example of this is frame.focus(), and another is a frame element
onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after
a postMessage dispatched from an inline script while the frame was
still loading.
To resolve these ordering concerns, this CL changes cross-process
postMessage to do a PostTask on the sender side before sending the
message to the browser process. This improves the current state of
the world, but does not yet achieve a perfect match for the IPC
ordering in the same-process case - see discussion on the bug.
Bug: 828529
Change-Id: I62a627c501526d09900be4f5bd2c899acf4d1e07
Reviewed-on: https://chromium-review.googlesource.com/999182
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#550284}
Reviewed-on: https://chromium-review.googlesource.com/1011287
Cr-Commit-Position: refs/heads/master@{#550621}
--
wpt-commits: f281334c36847064b75740239882e2684aee0437
wpt-pr: 10456
Automatic update from web-platform-testsAllow feature policy to be used in opaque origins.
Currently, policy-controlled features do not work as expected in
frames with opaque origins, such as isolated sandboxes and data: URLs,
because the eventual opaque origin of the frame is not known when the
HTMLFrameOwnerElement builds the container policy, and so has no way
to tell the browser that a particular origin should be allowed.
This CL adds a new member to the ParsedFeaturePolicyDeclaration, which
indicates that the iframe policy is expected to apply to the origin of
the frame, and is used when that frame has an opaque origin. This can
be triggered with an iframe of the form
<iframe sandbox allow="feature">
or
<iframe sandbox allow="feature src">
This flag is checked when building the feature policy in the new frame,
and ensures that the new feature policy will allow the feature in that
origin.
This is the first part of the eventual solution -- currently this has
the effect of allowing the feature even if a sandboxed frame navigates
to a new page (causing a new opaque origin to be created for it).
Subsequent CLs will add a unique identified to each such origin, and
ensure that the generated policies are properly tied to the specific
origin of the frame.
Bug: 690520
Change-Id: Ie18b9bc3c36be6550baf5a03e355871b9589fd40
Reviewed-on: https://chromium-review.googlesource.com/963382
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550463}
--
wpt-commits: 4c8580c189ce4501997af80b599bea070b1a7299
wpt-pr: 10076
Automatic update from web-platform-tests[css-typed-om] Support offset-rotate.
Introduces the <angle> data type.
Test fails because we compute offset-rotate to a pair rather than
'as specified'
had to rebaseline all the tests.
Bug: 820299
Change-Id: Ifdc192550b0b544b9887af80c259b3bfeede556b
Reviewed-on: https://chromium-review.googlesource.com/1003433
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550146}
--
wpt-commits: 1dd03e794199f6430072ecef144991112136cca5
wpt-pr: 10390
Automatic update from web-platform-testsFix race in track-stats.https.html test.
This resolves the onIceConnectionStateComplete probmise when
iceConnectionState reaches either 'connected' or 'completed' and fixes
the race if it had already reached these states before the function was
called.
This fix is speculative. I am no longer able to repro the TIMEOUT
locally with or without the fix.
Bug: 829401
Change-Id: I1dec90250d640d93498c59a932ab5e84a3b96f15
Reviewed-on: https://chromium-review.googlesource.com/1012029
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550580}
--
wpt-commits: a4accccea67a4de543edebaa51aa8c8b898aa323
wpt-pr: 10458
Automatic update from web-platform-testsMerge pull request #10429 from emilio/mutation-record
[cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked.
--
wpt-commits: ab9fc1edc3f464617d6ed72a2336d064f9cdcfcc
wpt-pr: 10429
Automatic update from web-platform-tests[css-typed-om] Support remaining misc properties.
Known failures:
- all: computed value is always "", it should compute to something...
- animation-name: <custom-ident> not mentioned in typed om spec.
- cursor: 'grab' and 'grabbing' are still webkit prefixed.
- list-style-type: Blink implements something different to the spec.
- page: computed value is always "", <custom-ident> not mentioned in
typedom spec
- perspective: '0' seems to compute to none.
- perspective-origin: Blink doesn't support 'none' keyword
- quotes: computed value is always ""
- size: computed value is always ""
- speak: Blink implements something different to the spec.
- transform-box: Blink doesn't support 'border-box' keyword
- z-index: computed value is always 'auto' (might be something to do
with stacking context)
Bug: 820299
Change-Id: I629dda1c4bcac92f59cae3bddf11bd375f98e5c2
Reviewed-on: https://chromium-review.googlesource.com/1003434
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550527}
--
wpt-commits: 071e621564bc4af04a04e8b8e515bfb306a6613e
wpt-pr: 10391
Automatic update from web-platform-testsStringify RequestInit.body
As specified, RequestInit.body should be stringified, i.e.,
{toString(): () => 'hi!'} should be treated as same as 'hi!'.
Bug: 831076
Change-Id: I4118c0faa9535d62b3db2529bf23716fdc25a997
Reviewed-on: https://chromium-review.googlesource.com/1004561
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550523}
--
wpt-commits: 96bceca65945e50c61128eaf5473fc9bc9e46c99
wpt-pr: 10394
Automatic update from web-platform-testsRemove http/tests/w3c
This CL moves the final user-timing tests to external/wpt and removes
the folder. The performance_entrylist_checker is changed as in the http
counterpart to allow de-duplicating test messages.
There are some tests that are related to the wpt counterparts, but not
equivalent and in a different format, so unifying some of these tests
can be done in the future.
Bug: 498037
Change-Id: I6f35d962ba088d92a9768e49a65dea4d5c267491
Reviewed-on: https://chromium-review.googlesource.com/1007888
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550310}
--
wpt-commits: 51704839c172ba8a70910bff484837c25adbfc9a
wpt-pr: 10434
Automatic update from web-platform-testsUse version-specific prefs files when running Firefox (#10443)
Firefox requires a prefs file to be loaded to ensure that it doesn't
make external network connections, and to make sure that other
settings are appropriate for testing. Previously we always used the
version of the prefs file from master, which is usually fine for
nightly builds, but doesn't work with release builds if it happens
that a pref changed.
This change uses the correct release version of the prefs file for
firefox releases and beta versions. It continues to use the master
version for any nightly build; this could be fixed in some cases if we
are able to access the actual commit hash used to build Firefox, but
probably isn't too bad an approximation.
The caching algorithm was changed so that release versions of the
prefs are cached forever, and the nightly version is updated once per
day (although this doesn't quite match the nightly release cadence,
it's only going to fail in edge cases where the prefs were changed in
the file, but the nightly version was not yet updated, of vice-versa.)
--
wpt-commits: cf2ef62f1c470b47a03275c795c6dedd69eace88
wpt-pr: 10443
Automatic update from web-platform-testsFix regression allowing text value for -webkit-background-origin
Fix regression allowing text value for -webkit-background-origin that
was caused by r514365.
Code change implemented by Bugs Nash, testcase by Rob Buis.
Bug: 802256
Change-Id: I11e2b1b19a374e9f6b9c1091d82882ef526bc63c
Reviewed-on: https://chromium-review.googlesource.com/1008102
Commit-Queue: Rob Buis <rob.buis@samsung.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550221}
--
wpt-commits: fc7af09fb3eea0ef511a061e5734c1dc8e539b0d
wpt-pr: 10447
Automatic update from web-platform-testsRename cakey.pem to cacert.key for consistency
And add a README with some basic instructions for newcomers.
--
wpt-commits: a5bb6d23ac757fcb5e8aef6fd7ed7587324982db
wpt-pr: 10445
--HG--
rename : testing/web-platform/tests/tools/certs/cakey.pem => testing/web-platform/tests/tools/certs/cacert.key
Automatic update from web-platform-testsUpdate marionette_driver from 2.5.0 to 2.6.0 (#10437)
--
wpt-commits: 0ac0ee7a22c2b8f6fd609a7986b104c75c5428bd
wpt-pr: 10437
Automatic update from web-platform-tests[css-layout-api] Fix DCHECK with the custom layout and multicol.
There are probably larger changes that need to happen to ensure that
the custom-layout and multicol play nicely together, but this removes
a DCHECK crash for now.
Bug: 823074
Change-Id: I98f4a34bd0c35e8cd3d23501ca64f38b96be9e7d
Reviewed-on: https://chromium-review.googlesource.com/990780
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550148}
--
wpt-commits: 976e2c1f4b37821272f303aee639b62e1fd085f9
wpt-pr: 10287
Automatic update from web-platform-testsS13nSW: Update wpt/service-workers/service-worker/navigation-preload/broken-chunked-encoding.https.html
Before this CL, the test expected that preloadResponse is
rejected when decoding a chunked body is failed. However preloadResponse
is supposed to be resolved once the headers are arrived. It should be
resolved instead of rejected. Update the test to expect that
preloadResponse is resolved even for broken chunked body.
With S13nSW enabled, this test will start passing but it wouldn't
pass w/o S13nSW.
This CL also adds a test case where broken chunked body is transfered
with delays.
Bug: 830472
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ibc2909dfc4537f209417a13cff63898ad39229a7
Reviewed-on: https://chromium-review.googlesource.com/1004562
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550061}
--
wpt-commits: 1dcdb61cb2eb054e6d16733d4eb4a6b56793b598
wpt-pr: 10395
Automatic update from web-platform-tests[css-typed-om] Support remaining multi-col properties.
To support column-count which takes <integer>s, we had implement integer
handling as resolved by:
https://github.com/w3c/css-houdini-drafts/issues/574#issuecomment-366845604
Basically, a non-integer passed to <integer> is 'out of range', so we
wrap it in a calc(). Coincidentally, column-count also needs to be
positive, so we had to change ComputedStyle::SetColumnCount to clamp.
Note that this doesn't change CSSOM behaviour, as the parser
would've rejected non-positive values so ComputedStyle only gets
positive values. Since Typed OM skips parsing, we have to clamp in
ComputedStyle as well.
Bug: 820299
Change-Id: Ia56e4bdb55826e72d46c66666addda168dea3d2a
Reviewed-on: https://chromium-review.googlesource.com/1001084
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550058}
--
wpt-commits: 0060eb41b1da8a5989772e12c034e14e8d025fae
wpt-pr: 10371
Automatic update from web-platform-testsAdd test for checking property order after setting property on CSSStyleDeclaration
--
wpt-commits: c5c79bb418341bb0b2ed304f1325cd522bf4306e
wpt-pr: 10354
Automatic update from web-platform-testsStop running tests on pypy (#10435)
I don't recall ever finding a real issue with these tests, but they
are flaky and take up valuable machine time in CI.
--
wpt-commits: 5a0d559e1acb9856b784e0d02e34856d9d8fad90
wpt-pr: 10435
The previous setup was altering sys.path in the wrong way and falling
foul of the module cache. It's easier just to import the parent module
using the underlying import functions directly than try to fix up the
paths.
MozReview-Commit-ID: IEDWCPwUgxg
--HG--
extra : rebase_source : 59c51f302f64a584472bbbfe6ad2116fa2266083
The PNG data generated in this test creates a 100x100 image with opaque green
pixels in the left 50px and fully transparent pixels in the right 49px. The 1px
vertical strip of pixels at pixel column 50 are green pixels with .66 alpha.
The test was failing because it supplied a shape-image-threshold of .25, and
thus was floating by 51px instead of the intended 50px. This change modifies
the test to use a shape-image-threshold of .7, generating the intended 50px
float area.
MozReview-Commit-ID: GJtym0p95yk
--HG--
extra : rebase_source : 338049a27e6e8af317f6cd61f96bd861f5909bd0
The test shape-outside-circle-027.html has two issues that prevent it from
matching the reference image. For that test to pass, the text must be floated
right by 75 pixels. The two issues are:
1) The circle is defined as 35% of 170 pixels, which calculates to 59.5px.
Since the shape-margin is 15px, this makes the total offset less than the
target of 75px.
2) The circle is offset upwards by 10 pixels, which introduces a slight angle
between the block start of the text and the center of the circle. The
cosine of this small angle is slightly less than 1, which reduces the
offset by some amount.
The changes made here specify the circle radius in whole pixels, and move the
center of the circle such that it is between the block start and block end of
the floated text, ensuring that the full width of the circle + shape-margin
will be used for calculating the float area.
MozReview-Commit-ID: JQ9Mc3GU4tW
--HG--
extra : rebase_source : 6e5a4c1da39bf85828286674d7aca14d0cf39181
https://www.w3.org/TR/css-shapes-1/#funcdef-ellipse states that the
grammar for ellipse is:
ellipse() = ellipse( [<shape-radius>{2}]? [at <position>]? )
This permits either 0 or 2 shape-radius tokens, but not 1. These two tests
use 1 shape-radius token and do not parse correctly.
https://www.w3.org/TR/css-shapes-1/#typedef-shape-radius states that omitted
shape-radius values default to closest-side. This change updates these two
tests to add the closest-side value for the missing shape-radius tokens.
MozReview-Commit-ID: 9UKxJel1b50
--HG--
extra : rebase_source : deeab3e7934e8060207e7c780a7881332478034f
https://www.w3.org/TR/CSS2/visudet.html#propdef-line-height specifies that
line-height is given an initial value of normal, which is defined:
Tells user agents to set the used value to a "reasonable" value based on the
font of the element. The value has the same meaning as <number>. We recommend
a used value for 'normal' between 1.0 to 1.2. The computed value is 'normal'.
These tests are designed to work correctly if and only if the line-height
is 1. This change specifies line-height: 1 explicitly.
MozReview-Commit-ID: 3Ueassok0f
--HG--
extra : rebase_source : acd09d577cd54a88c431fbfdc4dca88ec2afe3ec
The tests are currently under plain-text HTTP.
Since we are only shipping new features for secure origins,
a bunch of tests fail (even though they work with HTTPS).
The tests will be fixed in a followup.
MozReview-Commit-ID: 1iUjpwmLgho
--HG--
extra : rebase_source : 770fc4e725873fc42764d4cfd078b034d03aa280
This is simple mistake of bug 1451672.
EditorBase::CloneAttributesWithTransaction() sets both sourceElement and
destElement to aDestElement, but of course, it should set sourceElement to
aSourceElement.
Additionally, this patch adds mozilla specific web-platform tests to check
attribute cloning with basic edit operation.
MozReview-Commit-ID: GM1VjRHG7C3
--HG--
extra : rebase_source : 95427853442454525232df519ce5b5ad7bb12693
After closing the last top-level browsing context, the session
will be closed too.
MozReview-Commit-ID: CVsJpHO34BM
--HG--
extra : rebase_source : a43585aae5280c25cba7bd6b1e01cac44079797c
After closing the last top-level browsing context, the session
will be closed too.
MozReview-Commit-ID: CVsJpHO34BM
--HG--
extra : rebase_source : a43585aae5280c25cba7bd6b1e01cac44079797c
The test adjustments are:
A subtest of variable-presentation-attribute.html is marked as failure,
pending resolution of https://github.com/w3c/csswg-drafts/issues/2605.
font-parse-numeric-stretch-style-weight.html is updated to:
* handle calc per spec (invalid at computed-value time), see
https://github.com/w3c/csswg-drafts/issues/2590
* Accept 0% in font-stretch: https://github.com/w3c/csswg-drafts/issues/2591
* Accept font-weight descriptor ranges where the start is greater than the
end, per
https://drafts.csswg.org/css-fonts-4/#descdef-font-face-font-weight, which
says:
> User agents must swap the computed value of the startpoint and endpoint
> of the range in order to forbid decreasing ranges.
font-shorthand.html is updated to presumably fix a copy-paste error, where
"oblique 45deg" was expected to compute to "oblique", which is wrong.
The rest is removing failure annotations.
MozReview-Commit-ID: CNJ3LG71KRj
Automatic update from web-platform-testsDon't store logger on the Config object (#10430)
Config objects are shared between processes and so must be
pickleable. Loggers contain locks and so are not. Instead of storing
the logger on the config directly, store the logger name and level and
get the logger from the logging module each time.
--
wpt-commits: 03d76cc0bf283aead5520fd4137a7fc7607ee917
wpt-pr: 10430
wpt-commits: 03d76cc0bf283aead5520fd4137a7fc7607ee917
wpt-pr: 10430
Automatic update from web-platform-testsaccname: Updated tests (#10433)
* Add missing "hidden" style from several tests
* Fix expectations for several tests with presentation role used on img
* Fix bogus expectations on name and description calculations with combobox
* Fix incorrect whitespace in expectations for name from content with spans
* Add test for which coverage was missing
--
wpt-commits: 4cf7a66b04de7869777091b118892aac79659f6f
wpt-pr: 10433
wpt-commits: 4cf7a66b04de7869777091b118892aac79659f6f
wpt-pr: 10433
Automatic update from web-platform-testsAdd support for serializing the config as a dictionary.
This is required to pass the config into the wdspec tests.
--
s/host/browser_host/ in wdspec fixture
--
wpt-commits: ddcc729bca5abcc460db875952eb693b04fe2e41, 4b3342e16f320b69fef3c1809bb2614dc2109590
wpt-pr: 10431
wpt-commits: ddcc729bca5abcc460db875952eb693b04fe2e41, 4b3342e16f320b69fef3c1809bb2614dc2109590
wpt-pr: 10431
Automatic update from web-platform-tests[css-typed-om] Support remaining inline properties.
Failures because we don't support some keywords (difference between
CSS vs SVG?)
Bug: 820299
Change-Id: I1da06c5dfbd847a08b43d0bae42f969b4c40f1d7
Reviewed-on: https://chromium-review.googlesource.com/1002492
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549844}
--
wpt-commits: 9a2ba239ec826c0007352368d44fcfc02804ff16
wpt-pr: 10372
wpt-commits: 9a2ba239ec826c0007352368d44fcfc02804ff16
wpt-pr: 10372
Automatic update from web-platform-testsAdd python handler directory to Python path in wptserve (#10397)
Currently making import of files relative to the handler is tricky
because, unlike in normal Python, the script directory isn't on the
path.
This patch adds it to the path when executing the handler. It also
ensures that any modifications made to the path or to sys.modules are
rolled back after the handler has run.
--
wpt-commits: b3b6ea0b307a2a47cb19d1e843c7344769c410d9
wpt-pr: 10397
wpt-commits: b3b6ea0b307a2a47cb19d1e843c7344769c410d9
wpt-pr: 10397
Automatic update from web-platform-tests[css-typed-om] Support remaining svg properties.
Known failures:
- flood & stop opacity: we should be clamping between 0 and 1 like
'opacity'.
- paint-order: we seem to always compute to a list, but we should be
computing to as specified (Firefox has correct behaviour).
Bug: 820299
Change-Id: I0bcf29e07cb63516072bc3d0c307d0eadf2de6a3
Reviewed-on: https://chromium-review.googlesource.com/1002433
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549791}
--
wpt-commits: d44cd21c00741101f22d62772efc070ba59e8f04
wpt-pr: 10373
wpt-commits: d44cd21c00741101f22d62772efc070ba59e8f04
wpt-pr: 10373
Automatic update from web-platform-tests[css-typed-om] Support remaining text properties.
Known failures:
- letter-spacing: a <length> of 0 resolves to "normal", but should
compute to "0".
- line-break: "anywhere" not supported.
- overflow-wrap & word-wrap: "break-spaces" not supported
- word-spacing: "normal" should compute to "normal" and should be able
to set word-spacing to a <percentage>.
Bug: 820299
Change-Id: If5bac479521de6f1658a38a295df01de98f433f2
Reviewed-on: https://chromium-review.googlesource.com/1002340
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549783}
--
wpt-commits: 3b7b8db90148105a987cc367165f7551edd8519f
wpt-pr: 10375
wpt-commits: 3b7b8db90148105a987cc367165f7551edd8519f
wpt-pr: 10375
Automatic update from web-platform-tests[css-typed-om] Add support for scroll properties.
Test failures:
- scroll-snap-align should always compute to a pair (but we currently
compute to single keyword if specified).
- scroll-snap-type should compute to as specified (but we currently
compute to pair).
Bug: 820299
Change-Id: Id38cee967daef8ac5c0658b958d6e74445035a83
Reviewed-on: https://chromium-review.googlesource.com/999078
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549778}
--
wpt-commits: 387fba3809b776a98e6b11725c6d9a5be037bbca
wpt-pr: 10363
wpt-commits: 387fba3809b776a98e6b11725c6d9a5be037bbca
wpt-pr: 10363
Automatic update from web-platform-testsMake DOMTokenList.supports() case-insensitive
According to the DOM spec (https://dom.spec.whatwg.org/#dom-domtokenlist-supports)
the supports() method should compare the ASCII-lowercase transform of its input to
the list of tokens supported by the DOMTokenList.
Bug: 831166
Change-Id: I40903a307ffb949bbbbc99e02b56565cb81d00ed
Reviewed-on: https://chromium-review.googlesource.com/1005412
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549733}
--
wpt-commits: 2e8fa7ba82e6d796bf460567be21fbe3d4902568
wpt-pr: 10405
wpt-commits: 2e8fa7ba82e6d796bf460567be21fbe3d4902568
wpt-pr: 10405
Automatic update from web-platform-tests[KeyboardLock] Updating API to reject the first promise if lock is called twice
Per the W3C spec, when navigator.keyboard.lock() is called a second time (or
more), any previous, pending promises should be rejected. The old behavior
of the API was to reject the newest promise which is not correct.
As part of this cleanup, I am also using DomExceptions instead of raw strings
for the rejection. This allows us to clean up the test code (which fails if
a raw string is returned in the reject call).
BUG=680809
Change-Id: Ic4f2563a6ccc22a434f8e6079f1995d9e584f9aa
Reviewed-on: https://chromium-review.googlesource.com/1003472
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549719}
--
wpt-commits: 1bb2bd025c3729192ded265adfbd57079ada2c5e
wpt-pr: 10400
wpt-commits: 1bb2bd025c3729192ded265adfbd57079ada2c5e
wpt-pr: 10400
Automatic update from web-platform-testsWPT-fy Intel/user-timing/ tests
This change cleans up the remaining tests in http/tests/w3c/ directory in
preparation to delete it. It moves some tests to external/wpt and removes other
tests, which are duplicates:
* test_user_timing_entry_type.html is duplicated by entry_type.any.js
* test_user_timing_mark_exception.html duplicated by mark_exceptions.html
* test_user_timing_method_exist.html is duplicated by user_timing_exists.any.js
Bug: 498037
Change-Id: I1ba43eba81ed0a5d9e1e1a79aef11b9904556f69
Reviewed-on: https://chromium-review.googlesource.com/1002736
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549659}
--
wpt-commits: 827efec49afed216d98738b9cc60f63ca2bfc401
wpt-pr: 10385
wpt-commits: 827efec49afed216d98738b9cc60f63ca2bfc401
wpt-pr: 10385
Automatic update from web-platform-tests[css-typed-om] Add support for fill & stroke properties.
Some failures:
- fill & stroke shorthands do not seem to follow spec (it should be
list valued)
- fill-opacity & stroke-opacity do not clamp their values (ComputedStyle
should clamp values, like opacity).
- fill-color is not implemented.
Bug: 820299
Change-Id: I0879e353cd22291aa8a34f2a10895809b43d8aa5
Reviewed-on: https://chromium-review.googlesource.com/998454
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549499}
--
wpt-commits: d577e28a3e8db5d31b0e35ab3dcbd33304c1680f
wpt-pr: 10365
wpt-commits: d577e28a3e8db5d31b0e35ab3dcbd33304c1680f
wpt-pr: 10365
Automatic update from web-platform-tests[css-typed-om] Add support for font properties.
Had to modify the test harness to allow numbers in keywords. This
coincidentally fixed an error in one of the tests (transform-style).
Bug: 820299
Change-Id: Ia7e2854f38a5b960e6537d2c4ba309cb71c1e963
Reviewed-on: https://chromium-review.googlesource.com/999225
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549473}
--
wpt-commits: e62fc73167b0c090d687e7c4c632745c5e98860a
wpt-pr: 10362
wpt-commits: e62fc73167b0c090d687e7c4c632745c5e98860a
wpt-pr: 10362
Automatic update from web-platform-tests[css-typed-om] Fix unsupported values in non-list-valued properties.
Currently, when we reify a value, we try to first reify it as a single
value. If that fails, we try reifying it as a list value. This code
was written with the incorrect assumption that only list-valued
properties are stored as CSSValueLists. This is not true, as many single
valued properties (such as grid-auto-flow) are stored as CSSValueLists.
This patch adds an additional check so that only properties that are
explicitly marked as list-valued are reified as list values.
Bug: 829881
Change-Id: I965e38355b9859a43fcb1b940f19237f9f07fdf6
Reviewed-on: https://chromium-review.googlesource.com/1002214
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549455}
--
wpt-commits: cb4e20750f10c57702db9cfcf418dc5b33448489
wpt-pr: 10364
wpt-commits: cb4e20750f10c57702db9cfcf418dc5b33448489
wpt-pr: 10364
Automatic update from web-platform-testsImplement deprecation of content type sniffing for workers.
Allow control of the deprecation via runtime enabled features, with a first
step for logging a warning to the console, and the second step to block it
outright.
Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ
Change-Id: I1be1001cbbef152458119b1516750bb4f1d1e4de
Reviewed-on: https://chromium-review.googlesource.com/975611
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549495}
--
wpt-commits: d9a9bcf8b69debee46db030d75a1217325a9ca77
wpt-pr: 10331
wpt-commits: d9a9bcf8b69debee46db030d75a1217325a9ca77
wpt-pr: 10331
Automatic update from web-platform-testsMake sure table flex/grid items recalculate min/max widths.
We used to rely on this taking place lazily via
MinPreferredLogicalWidth(), but that method won't necessarily be called
if the table is a flex/grid item.
Bug: 810327
Change-Id: Ic817bd109544d4b9e961552d0a3a38f127e6e548
Reviewed-on: https://chromium-review.googlesource.com/1000781
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549479}
--
wpt-commits: 069680cf1da5c762e912246dbcc2d82a280cd48d
wpt-pr: 10384
wpt-commits: 069680cf1da5c762e912246dbcc2d82a280cd48d
wpt-pr: 10384
Automatic update from web-platform-testsTest box-shadow serialization (#9519)
Following https://github.com/w3c/csswg-drafts/issues/2305, the canonical serialization for box-shadow was changed from inset? && <length>{2,4} && <color>? to <color>? && <length>{2,4} && inset?. Convert an existing box-shadow text into a testharness.js test in order to test serialization as well.
--
wpt-commits: 5a93530d4db27df7a3154d9a5b75a0f36d592c6a
wpt-pr: 9519
wpt-commits: 5a93530d4db27df7a3154d9a5b75a0f36d592c6a
wpt-pr: 9519
Automatic update from web-platform-testsAdd external WPT test for cross-origin requests
The browser should not attach client hints to the
requests fetched from cross origins.
Bug: 817049
Change-Id: Ia7cedfbb6edaaf3616d6e2783965cc52f93c0cd9
Reviewed-on: https://chromium-review.googlesource.com/1000841
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549238}
--
wpt-commits: 46abbd55aa879ee92ce2f830819569936d9f531f
wpt-pr: 10352
wpt-commits: 46abbd55aa879ee92ce2f830819569936d9f531f
wpt-pr: 10352
Automatic update from web-platform-testsIn HTML documents, always make sure we a body (#10376)
--
wpt-commits: d258fe90d63872a39ea6c3b59074810c01bbf862
wpt-pr: 10376
wpt-commits: d258fe90d63872a39ea6c3b59074810c01bbf862
wpt-pr: 10376
Automatic update from web-platform-testsMove the config into its own class (#10231)
--
wpt-commits: bfef1f20a419d24633e48d24c14e6a7503e1d48c
wpt-pr: 10231
wpt-commits: bfef1f20a419d24633e48d24c14e6a7503e1d48c
wpt-pr: 10231
The (fast) internal reftest runner wasn't affected by this, so we
didn't notice the breakage since it only happened on platforms still
using the older broken runner.
MozReview-Commit-ID: AA2GOspOxgR
This test was frequently timing out in debug due to a short timeout in
the test.
MozReview-Commit-ID: KgbyGekWxE7
--HG--
extra : rebase_source : 94b99c7990c36727e54705f9cee17d83cfded9a7
