https://github.com/web-platform-tests/wpt

sort by:
Revision Author Date Message Commit Date
586299b Correct serialization of URL in background-332.html According to https://drafts.csswg.org/cssom/#serialize-a-url, the serialization of a URL always includes double-quotes, and per https://drafts.csswg.org/css-values/#relative-urls, if a URL appears in a computed style, it is resolved to an absolute URL. Adjust background-332.html to match the spec. 15 April 2018, 15:41:48 UTC
fd2badf [css-values] Typo fixes (#10383) 14 April 2018, 19:47:57 UTC
da5837a Reland "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} 14 April 2018, 15:47:16 UTC
6f621ca Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/37b8862d354e0014a72715462dd2102dd5b599cc . (#10470) 14 April 2018, 15:33:30 UTC
0e0344a Merge pull request #10422 from emilio/cssom-woes [cssom] Add tests for some recent CSSWG resolutions. 14 April 2018, 11:37:26 UTC
c53d084 Reland 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} 13 April 2018, 23:31:26 UTC
ae86013 Remove Element.createShadowRoot. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1453789 gecko-commit: b2dd9ca61e0b92b6a0da66d86de4ab4f87cd8e19 gecko-integration-branch: central gecko-reviewers: smaug 13 April 2018, 22:24:03 UTC
433d39e [cssom] Remove comment that now is invalid per CSSWG resolution. getComputedStyle returns styles in the node's document per the resolution in https://github.com/w3c/csswg-drafts/issues/1548. 13 April 2018, 20:20:18 UTC
dc670d8 [cssom] Test detached elements, elements outside the flattened tree, and hidden frames. This tests resolutions from https://github.com/w3c/csswg-drafts/issues/1548. 13 April 2018, 20:20:18 UTC
de23472 [cssom] Test that getComputedStyle with an unknown/invalid pseudo-element throws. This tests the resolution in https://github.com/w3c/csswg-drafts/issues/2149. 13 April 2018, 20:20:17 UTC
cb845c5 Revert "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} 13 April 2018, 20:09:27 UTC
e6cffaa Test 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 13 April 2018, 19:17:17 UTC
81bcc8d Make PointerEvent fromElement/toElement return null. Also added web-platform-tests. Blink intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/G2s1Ol3qcgA Closes https://github.com/w3c/pointerevents/issues/167 Bug: 827271 Change-Id: I8429b9541f8cfc38223b3a34116b74c2aba92ee5 Reviewed-on: https://chromium-review.googlesource.com/986877 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#550683} 13 April 2018, 18:25:25 UTC
6ad1b51 Revert "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/6886 https://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} 13 April 2018, 17:30:38 UTC
7b20d12 Merge pull request #10263 from csnardi/patch-10 Update serialization of timing functions 13 April 2018, 17:26:34 UTC
2707869 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} 13 April 2018, 17:03:30 UTC
1e5a5fe Merge pull request #10462 from ewilligers/background-serialization-variety Accept variation in serialization of 'background' 13 April 2018, 16:48:17 UTC
f281334 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} 13 April 2018, 15:40:47 UTC
f6787be Accept variation in serialization of 'background' Serialization of the CSS property 'background' varies across browsers. There is an open spec issue: https://github.com/w3c/csswg-drafts/issues/418 Until the issue is resolved, we accept a variety of serializations. 13 April 2018, 15:22:50 UTC
f90d3d6 Test serialisation of collections in wdspec. Ports tests added to Marionette in bug 1284232 to WPT. These test that the Arguments, Array, FileList, HTMLAllCollection, HTMLCollection, HTMLFormControlsCollection, HTMLOptionsCollection, and NodeList collections are properly serialised when returned from an injected script. There is one failing test that needs more investigation. My current suspicion is that it is a JavaScript bug. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1453009 gecko-commit: 172094bca9a6e2f841e629aae292647e212d92c6 gecko-integration-branch: central gecko-reviewers: whimboo 13 April 2018, 13:46:58 UTC
4c8580c Allow 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} 13 April 2018, 12:05:15 UTC
1dd03e7 [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} 13 April 2018, 12:04:14 UTC
a4acccc Fix 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} 13 April 2018, 11:11:53 UTC
ab9fc1e Merge pull request #10429 from emilio/mutation-record [cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked. 13 April 2018, 07:13:53 UTC
071e621 [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} 13 April 2018, 06:52:44 UTC
96bceca Stringify 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} 13 April 2018, 05:33:09 UTC
08c935c custom-elements: Implement customElements.upgrade(). Intent-to-implement-and-ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zCQe7UkR07w Bug: 819482 Change-Id: I5645d5711d7fe1323992533e6c73593ba59d1bca Reviewed-on: https://chromium-review.googlesource.com/1009450 Reviewed-by: Hayato Ito <hayato@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#550513} 13 April 2018, 05:02:00 UTC
bdcafae Let overflow parse two values. Per https://github.com/w3c/csswg-drafts/issues/2484. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1453148 gecko-commit: eaf30a1f59eedf65d4d6a5009bebfd014873d64e gecko-integration-branch: central gecko-reviewers: xidorn 12 April 2018, 21:08:22 UTC
96f16c5 Implement Request.destination. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1402892 gecko-commit: 284b35d145ffcdd31fd0ecfef5031aac1bc82553 gecko-integration-branch: mozilla-inbound gecko-reviewers: asuth, baku 12 April 2018, 20:53:29 UTC
5170483 Remove 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} 12 April 2018, 20:21:40 UTC
cf2ef62 Use 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.) 12 April 2018, 19:52:22 UTC
7e8bc61 Backed out changeset 0f81334efa0a (bug 1445883) for crashes (bug 1446902). a=backout (#10412) gecko-commit: 9fa586e87f34bef3bb15431d149ec7aeae0f7d24 gecko-integration-branch: central gecko-reviewers: backout 12 April 2018, 18:04:34 UTC
fc7af09 Fix 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} 12 April 2018, 16:51:35 UTC
56a257e Merge pull request #10170 from ewilligers/backgrounds-borders-parsing CSS Backgrounds and Borders 3 parsing tests 12 April 2018, 16:12:55 UTC
940c743 Update by testing Firefox nightly 61.01a 12 April 2018, 15:25:12 UTC
a5bb6d2 Rename cakey.pem to cacert.key for consistency And add a README with some basic instructions for newcomers. 12 April 2018, 15:15:45 UTC
0ac0ee7 Update marionette_driver from 2.5.0 to 2.6.0 (#10437) 12 April 2018, 14:35:14 UTC
e965af7 Return null from contentDocument/getSVGDocument() for cross-origin documents. Change-Id: I1e66f2cdc50be889b697b54401be6352607fa649 Reviewed-on: https://chromium-review.googlesource.com/1006528 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#550152} 12 April 2018, 12:36:50 UTC
976e2c1 [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} 12 April 2018, 12:27:52 UTC
19a42b9 followup: Remove a explicit testharness.css link to appease wptlint. on a CLOSED TREE bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1339656 gecko-commit: e90ac14a383f2a3ae97358d68dfcfc47f68e60c2 gecko-integration-branch: central gecko-reviewers: me 12 April 2018, 09:54:31 UTC
13758ad css-align] Upstream our shorthand serialization tests. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1339656 gecko-commit: 4ac4932953254018e6fbd110ab8ab5ca76885069 gecko-integration-branch: central gecko-reviewers: mats 12 April 2018, 09:54:31 UTC
b3a9b56 css-align] Don't restrict shorthand parsing now that's not ambiguous. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1339656 gecko-commit: 91ae8e15b175edc6e6e74b99f68fc155438b20ef gecko-integration-branch: central gecko-reviewers: mats 12 April 2018, 09:54:31 UTC
1dcdb61 S13nSW: 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} 12 April 2018, 07:31:12 UTC
0060eb4 [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} 12 April 2018, 07:22:00 UTC
2d4fbd4 Add tests for liveness of NodeLists/HTMLCollections (#8993) * Add tests for liveness of NodeLists/HTMLCollections - Node#childNodes - ParentNode#children - {Document,Element}#getElementsByTagName - {Document,Element}#getElementsByTagNameNS - {Document,Element}#getElementsByClassName - Document#images - Document#embeds - Document#plugins - Document#links - Document#forms - Document#scripts - Document#getElementsByName * Move liveness tests to each of API test files * Fixed a nit issue * Modify the test description 12 April 2018, 02:28:33 UTC
7bbb8d0 Stop generating stylo expectations. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1452113 gecko-commit: ea3453cc7d92df2539adeb45f390b9dfece2c4e6 gecko-integration-branch: central gecko-reviewers: jgraham 11 April 2018, 23:58:17 UTC
c5c79bb Add test for checking property order after setting property on CSSStyleDeclaration 11 April 2018, 22:47:46 UTC
6003ea3 Add webdriver.Element string representation. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1453084 gecko-commit: bdb78cb3d6d3cd0a5ebc31ee91a3c2590f54bb17 gecko-integration-branch: central gecko-reviewers: whimboo 11 April 2018, 21:38:48 UTC
7f13995 Add webdriver.Session string representation. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1453084 gecko-commit: 097b57bbeb46b0f3abc2b6fcec1c41a42d87f5da gecko-integration-branch: central gecko-reviewers: whimboo 11 April 2018, 21:38:48 UTC
5a0d559 Stop 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. 11 April 2018, 20:20:17 UTC
292f368 Remove usage of setTimeout to appease lint. 11 April 2018, 18:35:20 UTC
a747b36 [cssom] Add tests for removeProperty in its various ways. 11 April 2018, 18:28:04 UTC
03d76cc Don'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. 11 April 2018, 18:24:29 UTC
4cf7a66 accname: 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 11 April 2018, 17:42:30 UTC
4b3342e s/host/browser_host/ in wdspec fixture 11 April 2018, 16:48:12 UTC
ddcc729 Add support for serializing the config as a dictionary. This is required to pass the config into the wdspec tests. 11 April 2018, 16:48:12 UTC
a31d306 Part 9: Fix wpt reftest shape-image-025.html to make every frame of the animated GIF use a green box in the lower-left quadrant. This test is designed to check that the float area is calculated from the first frame of an animated GIF. The reference rendering is a solid green square with the lower-left of the square supplied by the pixels in the GIF. Frame 2 of the GIF has white pixels in that quadrant. If layout is completed and onload is fired while frame 2 is showing, the test will fail even though the float area has been correctly calculated. This change puts green in the lower-left quadrant of all frames of the GIF so that the test is only testing the float area and not also testing that onload fires while a certain frame is showing. Note that this change doesn't impact the thoroughness of how we're testing shape-outside because it changes only the color of the pixels and not their opacity, and the float area is calculated from the alpha of the pixels. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404222 gecko-commit: 491be7851cfc3e4959af6e22a1adf70d5f7bb168 gecko-integration-branch: central 11 April 2018, 16:39:02 UTC
6b2fe34 Part 8: Fix wpt reftest shape-image-001.html to correct a too-wide container. The test currently stretches a 100 x 100 image to 150 pixels wide, which makes the shaded region of the png stretch to 75 pixels. None of the math in the rest of the test accounts for this stretching, and the test fails on all browsers. It seems clear that the intention was to use an unstretched, 100 pixel wide image, which makes the test pass. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404222 gecko-commit: 1c17b43d22afbd5e25f6d29c9168f2316b36103b gecko-integration-branch: central gecko-reviewers: dholbert 11 April 2018, 16:39:02 UTC
ccd2afa Part 5: Add web-platform-tests for linear-gradient with writing-modes. There's no shape-outside: <image> test with writing-modes on web-platform-tests, so I added some. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404222 gecko-commit: c489650a973000342cb667442321900d904e049e gecko-integration-branch: central gecko-reviewers: dholbert 11 April 2018, 16:39:02 UTC
1cda980 Part 4: Replace hash '#' with %23 in SVG data URIs, to fix XML parse errors. The hash symbol '#' is reserved as fragment identifier per bug 1430526 comment 1, so fix the test cases. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404222 gecko-commit: bd731b1a68618f1cbce43ce8f46711fafe08fb6e gecko-integration-branch: central gecko-reviewers: dholbert 11 April 2018, 16:39:02 UTC
9bc2e74 Use unicode-segmentation to iterate graphemes instead of chars (#10220) bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1396823 gecko-commit: 9b506268413c213ac701c8b46dd6e312625f4ce7 gecko-integration-branch: central gecko-reviewers: ato 11 April 2018, 16:28:45 UTC
6571e31 Add a WPT test to verify dedicated workers have a separate client ID from their owning document. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1451124 gecko-commit: aed7d4d9be32f8806138d2a23f4b8b0332498085 gecko-integration-branch: central gecko-reviewers: asuth 11 April 2018, 14:50:18 UTC
6e61ed2 Improve error when unable to find SSL key or cert. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1321517 gecko-commit: c7abc1d5b6ec9d32f54745f51e96065a89b774bf gecko-integration-branch: central gecko-reviewers: ato 11 April 2018, 14:49:00 UTC
f313b14 [cssom] Add a test for mutation records with invalid values. Should bail out before per step 5 of https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setpropertyvalue. 11 April 2018, 14:18:17 UTC
002991d Check for FTP subresource after applying CSP. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404744 gecko-commit: b2c0699b9bd405300986bc26f256e8bb9c0c53a7 gecko-integration-branch: central gecko-reviewers: ckerschb 11 April 2018, 14:16:05 UTC
3ed3aad Change more web-platform tests to avoid using FTP. CLOSED TREE bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404744 gecko-commit: 42cda784d2c54c8730e7fd218a00fb5846263e76 gecko-integration-branch: central gecko-reviewers: me 11 April 2018, 14:16:05 UTC
6d1dd02 Simple sub-resource only test. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1404744 gecko-commit: 1035ca43655e0bc157804943c21729d4a27823cd gecko-integration-branch: central gecko-reviewers: ckerschb 11 April 2018, 14:16:05 UTC
f11929f [cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked. https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setpropertyvalue always ends up in https://drafts.csswg.org/cssom/#update-style-attribute-for (step 8), which calls https://dom.spec.whatwg.org/#concept-element-attributes-set-value, which does queue a mutation record even if the value doesn't change. This makes this consistent with setAttribute("style", getAttribute("style")), for example. 11 April 2018, 14:12:06 UTC
9b7e9ba Disable test_pause_dblclick bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1432105 gecko-commit: f424114c6a2ccb65c256f42a835377eeb0f92d5c gecko-integration-branch: central gecko-reviewers: whimboo 11 April 2018, 13:24:57 UTC
cf39c87 Stop pointer action tests from restarting Firefox bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1432105 gecko-commit: f6b8d9c6cbfa3b4a1b0437cee337ff636b3cfcbe gecko-integration-branch: central gecko-reviewers: whimboo 11 April 2018, 13:24:57 UTC
7967c43 Merge pull request #10415 from w3c/font-variant-descriptor Font variant descriptor 11 April 2018, 11:39:34 UTC
9a2ba23 [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} 11 April 2018, 10:37:10 UTC
5d9948b Add tests for transferring ImageBitmap objects. 11 April 2018, 09:31:37 UTC
98cc5c8 quick test to see if descriptor supported anywhere 11 April 2018, 09:30:00 UTC
17b7215 Don't reparse stylesheets when assigning empty string to empty element. Per spec, assinging an empty string to textContent or innerHTML should not trigger any mutation observers, and therefore should not trigger a stylesheet reparse, when the element is already empty. Since we need to apply some special handling to innerHTML and textContent assignments to <style> nodes, and therefore re-parse directly in the setter rather than in response to mutation observers, we need to special-case this scenario. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1451940 gecko-commit: 95438fe6d5a87270b1ad713da14f123b17faaea2 gecko-integration-branch: central gecko-reviewers: bz 11 April 2018, 09:24:42 UTC
991a413 update rel help (#10188) 11 April 2018, 08:53:36 UTC
b3b6ea0 Add 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. 11 April 2018, 07:48:44 UTC
d44cd21 [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} 11 April 2018, 06:39:21 UTC
e6f6bbf [css-typed-om] Support remaining mask properties. Known failures: - clip-path: doesn't support <geometry-box> Bug: 820299 Change-Id: I28e00e59cfa7f7c3d2bd7db307fb6d0f528d395d Reviewed-on: https://chromium-review.googlesource.com/1002342 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#549788} 11 April 2018, 06:31:29 UTC
3b7b8db [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} 11 April 2018, 06:22:24 UTC
387fba3 [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} 11 April 2018, 06:04:09 UTC
2e8fa7b Make 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} 11 April 2018, 02:40:01 UTC
1bb2bd0 [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} 11 April 2018, 02:01:27 UTC
6934f15 Automate more focus tests with testdriver (#10396) 11 April 2018, 01:41:15 UTC
827efec WPT-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} 10 April 2018, 22:38:25 UTC
51615f8 Test descendant invalidation for :host(..). bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1452640 gecko-commit: 00ac14e011212f55d75afd6043ac8e41636dec5f gecko-integration-branch: central gecko-reviewers: xidorn 10 April 2018, 21:22:53 UTC
e504871 added special keys note (#10403) 10 April 2018, 18:20:46 UTC
1e801bf Revert "Enable ConsumeGestureOnNavigation by default" This reverts commit 2ca250d409adfa73a666daabd3ba19b94d6443a7. Reason for revert: A leak bot complains navigation-consumes-user-activation.tentative.sub.html is leaking. Sample build: https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/17509 Original change's description: > Enable ConsumeGestureOnNavigation by default > > See blink-dev thread: > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/kPli8ZCUeok > > A browser test is moved to be a tentative WPT due to this change. > > Bug: 772515 > Change-Id: Icf99c8c303c5055dcbcdace6ae94e3fcd1a01921 > Reviewed-on: https://chromium-review.googlesource.com/980599 > Reviewed-by: Nasko Oskov <nasko@chromium.org> > Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> > Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> > Commit-Queue: Charlie Harrison <csharrison@chromium.org> > Cr-Commit-Position: refs/heads/master@{#549293} TBR=nasko@chromium.org,mustaq@chromium.org,csharrison@chromium.org,kereliuk@chromium.org Change-Id: I0c998798d1367be61c633db76429c18ac554e4ff No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 772515 Reviewed-on: https://chromium-review.googlesource.com/1003437 Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#549363} 10 April 2018, 14:00:49 UTC
1a57aef Enable ConsumeGestureOnNavigation by default See blink-dev thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/kPli8ZCUeok A browser test is moved to be a tentative WPT due to this change. Bug: 772515 Change-Id: Icf99c8c303c5055dcbcdace6ae94e3fcd1a01921 Reviewed-on: https://chromium-review.googlesource.com/980599 Reviewed-by: Nasko Oskov <nasko@chromium.org> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#549293} 10 April 2018, 14:00:49 UTC
d577e28 [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} 10 April 2018, 13:52:24 UTC
e62fc73 [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} 10 April 2018, 13:36:34 UTC
cb4e207 [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} 10 April 2018, 13:35:49 UTC
d9a9bcf Implement 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} 10 April 2018, 13:16:58 UTC
069680c Make 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} 10 April 2018, 11:06:35 UTC
fd10426 Firefox serialition 10 April 2018, 09:59:10 UTC
429e62e Fix #10388: Make resources/test use the upstream config (#10393) 10 April 2018, 08:02:47 UTC
5a93530 Test 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. 10 April 2018, 07:52:00 UTC
149eff7 Tests for non-functional :host selector. Both Blink and WebKit pass the added tests. But of course all this stuff was untested initially, and my initial naive implementation would fail them. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=992245 gecko-commit: 5a24374d10f7b33f2582519664a21612c18f8cfb gecko-integration-branch: central gecko-reviewers: xidorn 09 April 2018, 22:40:06 UTC
46abbd5 Add 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} 09 April 2018, 19:28:09 UTC
d258fe9 In HTML documents, always make sure we a body (#10376) 09 April 2018, 17:31:56 UTC
back to top