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

sort by:
Revision Author Date Message Commit Date
90df068 WPT: Add cross-origin iframe focus test. Check that the correct value of activeElement in an iframe after losing focus in the parent frame. The behaviour is wrong in Chrome + OOPIF. BUG=755023 Change-Id: I30b3cdce0842115ba9e8249181bf25eb84bb8214 31 October 2017, 15:58:07 UTC
58b7239 [runner]: Tighten HTTPS check. (#8016) I forgot that `.` has meaning in regex. Whoops! 31 October 2017, 12:40:39 UTC
5676b48 [Fetch API] Propagate "keepalive" property to ServiceWorker Bug: 695939 Change-Id: If45e944d34eba2f9cd81f8e0a3e60cebc73e365b Reviewed-on: https://chromium-review.googlesource.com/737498 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#512801} 31 October 2017, 11:56:25 UTC
673e52d Update docs to note css/ exists 31 October 2017, 11:24:23 UTC
11ffb6b Move CSS testsuites at the root into css/ 31 October 2017, 11:24:23 UTC
1f0d883 Fix #7503: Get rid of versions in CSS testsuite directories 31 October 2017, 11:24:23 UTC
42a1277 Make concrete sensor IDL tests use standalone IDL files (#8004) * Make concrete sensor IDL tests use standalone IDL files Concrete sensor APIs: Accelerometer, Gyroscope, Magnetometer, Orientation Sensor 31 October 2017, 11:08:04 UTC
470d148 If canMakePayment() throws, it must be NotAllowedError. (#8009) 31 October 2017, 10:47:43 UTC
a0c5ba6 Fix whitespace error in 'empty' file (#8010) 30 October 2017, 16:32:51 UTC
1369b36 Allow firefox to run ssl tests without certutil Support for allowInsecureCerts was recently added to marionette, so we can get similar behaviour to Chrome where certificate validity is not checked during tests. To enable this we pass acceptInsecureCerts: True to the marionette session. However we should still use certutil when possible since that's closer to the standard browser codepath. This also requires a new release of marionette_driver since something changed in capability passing. 30 October 2017, 14:47:23 UTC
14cfa4d Merge pull request #8008 from w3c/sync_3922fb3e43b75d2ff118a5ebf793180f570fdb53 Merge pull request #8008 from sync_3922fb3e43b75d2ff118a5ebf793180f570fdb53 30 October 2017, 13:26:20 UTC
dfe81a6 Merge pull request #8007 from w3c/sync_c3004c057a96ac38d6216c74cef4e0e3c6d955c8 Merge pull request #8007 from sync_c3004c057a96ac38d6216c74cef4e0e3c6d955c8 30 October 2017, 13:26:09 UTC
3922fb3 style: Add a test for calc() inside animation-iteration-count. Upstreamed from https://github.com/servo/servo/pull/19005 [ci skip] 30 October 2017, 13:25:59 UTC
c3004c0 style: Add some more tests for disallowed rootMargin values. Upstreamed from https://github.com/servo/servo/pull/18917 [ci skip] 30 October 2017, 13:25:59 UTC
4ceeda7 Worklet: Make WorkletGlobalScope inherit parent document's ReferrerPolicy The Worklet spec defines the referrer policy as follows: "5. Let inheritedReferrerPolicy be outsideSettings's referrer policy." https://drafts.css-houdini.org/worklets/#script-settings-for-worklets However, our current impl sets the referrer policy to an empty String. This CL makes WorkletGlobalScope inherit outsideSettings's referrer policy, that is, parent Document's referrer policy. <Details of this change> Before this CL, GlobalScopeCreationParams is created with a string representing a referrer policy on the main thread and then it's parsed on a worker thread. This flow doesn't match the Worklet spec because Worklets inherit the Document's referrer policy that is already parsed. To handle it, this CL changes GlobalScopeCreationParams's referrer policy field from a string to ReferrerPolicy, and also changes places to parse the referrer policy header from a worker thread to the main thread for Workers. Also, this CL adds WPT tests for the referrer policy on Worklets. Bug: 773921 Change-Id: Id8b9aa6649bdd1c2851f8d64af230b24ebf1e78e Reviewed-on: https://chromium-review.googlesource.com/737311 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#512470} 30 October 2017, 12:01:46 UTC
5baacb9 Fix manifest upload filename 30 October 2017, 11:43:56 UTC
dea773e Remove test check that we don't get loggng output 30 October 2017, 11:11:29 UTC
6f31327 Don't use requests for manifest download. This would require requests to always be installed into a venv in travis since before_install can download the manifest. 30 October 2017, 11:11:29 UTC
c42b650 Support downloading the manifest in wptrunner. This currently depends on being in a wpt tree from GitHub so is off my default for wptrunner and on by default for wpt run 30 October 2017, 11:11:29 UTC
1004eee Support manifest downloads in |wpt manifest| 30 October 2017, 11:11:29 UTC
fed6975 Add a script for downloading a manifest file from GitHub. mach wpt manifest-download will attempt to download and extract a recent MANIFEST.json file from GitHub, to speed up the manifest generation process. 30 October 2017, 11:11:29 UTC
61108a4 Upload the manifest as MANIFEST-<REV>.json.gz Since otherwise the metadata doesn't include the git rev 30 October 2017, 11:11:29 UTC
c146881 [runner]: Allow cross-origin tests. Currently, the test runner depends upon direct execution of 'completion_handler()' from inside the test window. This works fine as long as both windows are same-origin, but fails in cases where the test needs to execute on a distinct origin (to ensure that it executes in a secure context, for instance). This patch shifts the test runner away from this direct execution model, onto the 'complete' message that the test window sends upon completion. 30 October 2017, 10:03:00 UTC
1519188 Make Ambient Light Sensor IDL tests use a standalone IDL file (#7861) * Make Ambient Light Sensor IDL tests use a standalone IDL file This also adds the support to idlharness.js to filter which members/etc. are added from a chunk of IDL text, fixing https://github.com/w3c/web-platform-tests/issues/7781. Before and after the changes, there are 2 failing tests in Chrome Dev, both due to the hasReading attribute. 30 October 2017, 01:47:33 UTC
8e42915 Update the link to spec in websockets/README.md 28 October 2017, 05:48:43 UTC
75f40af Add some PEP 484 type hints to utils.py (#7987) 27 October 2017, 15:11:55 UTC
0190172 Merge pull request #7972 from w3c/more-font-3-updates Several more CSS 3 Fonts tests for previously untested features 27 October 2017, 10:42:59 UTC
6f1c28f Allow space-separated host names in hosts file. My new Ubuntu install decided to teach me more about the format of the hosts file. 27 October 2017, 10:20:21 UTC
31677af Add a state file existence check This prevents `LOG: MainThread DEBUG IOError loading stored state` Which is a little misleading (and the next log line is `No existing state found`, which is the expected message) 27 October 2017, 10:20:00 UTC
7abd60c Move check-layout-th.js script to resources/ folder This file was duplicated in the different tests suites that were using it, currently css-flexbox-1, css-grid-1 and css-tables-3. This script is useful to validate the position and sizes of an element using arguments like "data-expected-with" and other. We could put it somewhere under css/ but that won't solve the relative paths issue we are facing. On top of that there are some CSS suites that are directly in the root web-platform-tests folder (and not under css/) and might want use this script in the future. This fixes issue #7969 by removing the duplicated copies of the script and moving it to resources/ root folder. It modifies the path in all the tests that were using it. 27 October 2017, 10:18:55 UTC
a4dc0a9 Another step towards porting blink CSP tests to WPT (script-src) This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - get rid of checkreport in tests that don't actually require it This should unblock `checkreport` changes that break the upstream integration. Bug: 651742 Change-Id: I22a98dff6da08d766bf3912fde88bddb31fc7d1c Reviewed-on: https://chromium-review.googlesource.com/738142 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#512120} 27 October 2017, 08:27:53 UTC
f7c76be Implemented the report-to functionality for webkit-residing csp The reporting api can now be used to send csp reports Did not yet implement the content csp version of this change. spec: https://wicg.github.io/reporting/ Bug: 726634 Change-Id: Icd5cc5699d31d0300e2bcfc6f72b636e855679ea Reviewed-on: https://chromium-review.googlesource.com/629083 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Julia Tuttle <juliatuttle@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#512107} 27 October 2017, 07:39:23 UTC
97caf42 Reland "Rename CSS scroll-boundary-behavior to overscroll-behavior" Updated core/BUILD.gn to replace old references with new ones. I cannot find a trybot that runs the noop builder test. So I did the following to help ensure this does not break noop builders: (1) - Run: ninja -w 'dupbuild=err' -C ./out/default/ -j 1024 chrome all (on a clean directory) - Run: ninja -w 'dupbuild=err' -C ./out/default/ -j 1024 chrome all Without my changes the second build was doing work but with my change the second build does nothing. AFAICT no-op test expect the second one. (2) grep -R "PropertyAPIScrollBoundary" Made sure the above does not find anything given that those files are renamed. This is a reland of 74e8a0f74fc589a58258655f59aa7f1efa666155 Original change's description: > Rename CSS scroll-boundary-behavior to overscroll-behavior > > The name change was decided here [1]. > > This is the minimal patch to change the publicly exposed CSS property. > It is intentionally small to make it easier to merge with M63. So, > internally Blink and content still use ScrollBoundaryBehavior name which will > be updated in the follow up patch larger patch. > > > [1] https://github.com/WICG/scroll-boundary-behavior/issues/24 > > Bug: 776776 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Change-Id: Iaa6ad62253ed7fe9ed7f0ee9865ffda852b17801 > Reviewed-on: https://chromium-review.googlesource.com/737090 > Reviewed-by: Dimitri Glazkov <dglazkov@chromium.org> > Reviewed-by: Sandra Sun <sunyunjia@chromium.org> > Commit-Queue: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#511493} TBR: dglazkov@chromium.org, pdr@chromium.org Bug: 776776 Change-Id: I319c110bb27181fed7b3e1c75ae0534928958612 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/740061 Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#511985} 26 October 2017, 22:38:14 UTC
fabf91d Add WPT tests for ConstantSourceNode Copy Chrome's tests for ConstantSourceNode to WPT. Until we coordinate better with other vendors, place everything in the wpt/webaudio/chrome directory. Changes from Chrome's version: * audit.js: * Deleted _logError function (but left the call in). * Changed console.log (in a comment) to just log (to satisfy presubmit check). * Remove Audit.loadFileFromURL. * audit-util.js: * Deleted everything having to do with writing out WAV files. Bug: 745778 Change-Id: Ib4adc73993a6c7e88c951b9cf213126b4396f9a1 Reviewed-on: https://chromium-review.googlesource.com/726268 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#511944} 26 October 2017, 21:00:59 UTC
7a384ee Modified the setRemoteDescription-offer.html Modifed the setRemoteDescription-offer tests to unblock the CL (https://webrtc-review.googlesource.com/c/src/+/9621). The peerconnection should only set the remote offer generated by the CreateOffer method. SetLocalDescription is called before creating a subsequent offer. To support unfied plan SDP, the m= section should be enforced in the subsequent offer and the offer with different order would be rejected. For example, if the first offer has "data" and the second offer with "audio, data" would be rejected. Based on a Github PR: https://github.com/w3c/web-platform-tests/pull/7893/files Bug: chromium:773620 Change-Id: Id947c05e795f9fabd60200a20adad02d278218bd Reviewed-on: https://chromium-review.googlesource.com/736318 Commit-Queue: Zhi Huang <zhihuang@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#511902} 26 October 2017, 19:48:37 UTC
f878fee Rename viewport/ to visual-viewport/ Per discussion in https://github.com/WICG/admin/pull/44. 26 October 2017, 19:44:49 UTC
95311d9 Add OWNERs to viewport tests 26 October 2017, 19:41:17 UTC
b474d5e HTML: Test behavior of HTMLElement focus(options) with preventScroll Per https://github.com/whatwg/html/pull/2787 This does not test what the expected scroll alignment should be for focus(), other than expecting that it be scrolled entirely into view. 26 October 2017, 19:11:08 UTC
a419e4e HTML: Update IDL for focus(options) Per https://github.com/whatwg/html/pull/2787 26 October 2017, 17:18:10 UTC
e166575 Activation Delegation: Add web platform tests Add web platform tests for the delegateStickyUserActivation attr. The tests are expected to fail for now since the attribute code has not landed. BUG=766090 Change-Id: Ieadc9c57b91bbe7ae78ba3e29c17fdf2efd09997 Reviewed-on: https://chromium-review.googlesource.com/735485 Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#511821} 26 October 2017, 15:48:36 UTC
dd83f89 Update secure contexts tests. This patch contains two sets of changes 1. The secure context WPT suite currently depends on a few behaviors that aren't shared between Chrome and Firefox. For instance, Chrome throws in the `Worker()` constructor in some places that Firefox doesn't, and Firefox supports nested Workers. While Chrome is catching up in these areas, we should harden the tests such that they still execute in these distinct environments. 2. After w3c/webappsec-secure-contests#42, the popup tests no longer match the spec. This patch brings them into line. Change-Id: If37b89dc77abec378147a9734e0c2804fc2e22a0 Reviewed-on: https://chromium-review.googlesource.com/732989 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#511817} 26 October 2017, 15:29:56 UTC
a39fc68 Another last step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - get rid of checkreoport in tests that don't actually require it This should unblock `checkreport` changes that break the upstream integration. Bug: 651742 Change-Id: Ic65772f02afd8b2031313323a1552b538a03d222 Reviewed-on: https://chromium-review.googlesource.com/738374 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#511797} 26 October 2017, 14:44:40 UTC
ec3d9c4 Revert "Reland "Rename CSS scroll-boundary-behavior to overscroll-behavior"" This reverts commit b8a6823aaad68dc08f41c116fc06fd1b097c04c6. Reason for revert: Somewhat speculative, but looks like this broke noop builds at least on Windows: https://uberchromegw.corp.google.com/i/chromium/builders/Win%20x64/builds/15892 Original change's description: > Reland "Rename CSS scroll-boundary-behavior to overscroll-behavior" > > This is a reland of 74e8a0f74fc589a58258655f59aa7f1efa666155 > The only change is in third_party/WebKit/Source/core/BUILD.gn > where an outdated generated file was updated with a new name. > > Original change's description: > > Rename CSS scroll-boundary-behavior to overscroll-behavior > > > > The name change was decided here [1]. > > > > This is the minimal patch to change the publicly exposed CSS property. > > It is intentionally small to make it easier to merge with M63. So, > > internally Blink and content still use ScrollBoundaryBehavior name which will > > be updated in the follow up patch larger patch. > > > > > > [1] https://github.com/WICG/scroll-boundary-behavior/issues/24 > > > > Bug: 776776 > > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > > Change-Id: Iaa6ad62253ed7fe9ed7f0ee9865ffda852b17801 > > Reviewed-on: https://chromium-review.googlesource.com/737090 > > Reviewed-by: Dimitri Glazkov <dglazkov@chromium.org> > > Reviewed-by: Sandra Sun <sunyunjia@chromium.org> > > Commit-Queue: Majid Valipour <majidvp@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#511493} > > Bug: 776776 > TBR: dglazkov@chromium.org, pdr@chromium.org > Change-Id: If9198d1eb0c7d0a4a4955a40e03e456f21275589 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Reviewed-on: https://chromium-review.googlesource.com/738295 > Reviewed-by: Majid Valipour <majidvp@chromium.org> > Commit-Queue: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#511677} TBR=majidvp@chromium.org,sunyunjia@chromium.org,dglazkov@chromium.org Change-Id: Iab2206926e649f759f5b18c546486546520cb2c6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 776776 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/738335 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#511737} 26 October 2017, 04:55:22 UTC
47305f0 service worker: Improve WPT test for FetchEvent for fetch() with request body Adds one test for a simple string body and one test for a Blob body into fetch-event.https.html. The Blob body test is moved from request-body-blob.https.html. Change-Id: I094ef1935a397d9ad11a1fc45210834ba7b242a1 Reviewed-on: https://chromium-review.googlesource.com/737469 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#511720} 26 October 2017, 03:36:52 UTC
a3ef21b Reland "Rename CSS scroll-boundary-behavior to overscroll-behavior" This is a reland of 74e8a0f74fc589a58258655f59aa7f1efa666155 The only change is in third_party/WebKit/Source/core/BUILD.gn where an outdated generated file was updated with a new name. Original change's description: > Rename CSS scroll-boundary-behavior to overscroll-behavior > > The name change was decided here [1]. > > This is the minimal patch to change the publicly exposed CSS property. > It is intentionally small to make it easier to merge with M63. So, > internally Blink and content still use ScrollBoundaryBehavior name which will > be updated in the follow up patch larger patch. > > > [1] https://github.com/WICG/scroll-boundary-behavior/issues/24 > > Bug: 776776 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Change-Id: Iaa6ad62253ed7fe9ed7f0ee9865ffda852b17801 > Reviewed-on: https://chromium-review.googlesource.com/737090 > Reviewed-by: Dimitri Glazkov <dglazkov@chromium.org> > Reviewed-by: Sandra Sun <sunyunjia@chromium.org> > Commit-Queue: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#511493} Bug: 776776 TBR: dglazkov@chromium.org, pdr@chromium.org Change-Id: If9198d1eb0c7d0a4a4955a40e03e456f21275589 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/738295 Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#511677} 26 October 2017, 01:43:32 UTC
16bf6bb Add safety check for missing kwargs (#7960) Prevents KeyError, which isn't important when intending to set the value anyway. 25 October 2017, 20:52:41 UTC
15b0fb3 Revert "Rename CSS scroll-boundary-behavior to overscroll-behavior" This reverts commit 74e8a0f74fc589a58258655f59aa7f1efa666155. Reason for revert: This caused an issue on Linux64 no-op build. Bug: 778310 Original change's description: > Rename CSS scroll-boundary-behavior to overscroll-behavior > > The name change was decided here [1]. > > This is the minimal patch to change the publicly exposed CSS property. > It is intentionally small to make it easier to merge with M63. So, > internally Blink and content still use ScrollBoundaryBehavior name which will > be updated in the follow up patch larger patch. > > > [1] https://github.com/WICG/scroll-boundary-behavior/issues/24 > > Bug: 776776 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Change-Id: Iaa6ad62253ed7fe9ed7f0ee9865ffda852b17801 > Reviewed-on: https://chromium-review.googlesource.com/737090 > Reviewed-by: Dimitri Glazkov <dglazkov@chromium.org> > Reviewed-by: Sandra Sun <sunyunjia@chromium.org> > Commit-Queue: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#511493} TBR=majidvp@chromium.org,sunyunjia@chromium.org,dglazkov@chromium.org Change-Id: I1d71b71c5d3c263fb2ff13c9d7a9184399df946f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 776776 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/738294 Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#511515} 25 October 2017, 18:28:47 UTC
511cb08 Added an IdleDeadline object for the test (#7478) 25 October 2017, 18:06:29 UTC
ede0592 Rename CSS scroll-boundary-behavior to overscroll-behavior The name change was decided here [1]. This is the minimal patch to change the publicly exposed CSS property. It is intentionally small to make it easier to merge with M63. So, internally Blink and content still use ScrollBoundaryBehavior name which will be updated in the follow up patch larger patch. [1] https://github.com/WICG/scroll-boundary-behavior/issues/24 Bug: 776776 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Iaa6ad62253ed7fe9ed7f0ee9865ffda852b17801 Reviewed-on: https://chromium-review.googlesource.com/737090 Reviewed-by: Dimitri Glazkov <dglazkov@chromium.org> Reviewed-by: Sandra Sun <sunyunjia@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#511493} 25 October 2017, 17:20:42 UTC
dd83144 fix stupid linting errors because trailing whitespace is the biggest single problem with tests ffs 25 October 2017, 15:32:44 UTC
e2fa5a1 Implement keepalive flag on Request This CL implements "keepalive" flag on Request behind an experimental flag. Currently it has some restrictions. - Quota is not at all implemented. - Non-simple requets are not supported. - The request property is not propagated to service worker. Bug: 695939 Change-Id: Icafb6268e2c8cde86c6d08e0edb940af7be1c525 Reviewed-on: https://chromium-review.googlesource.com/730443 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#511440} 25 October 2017, 14:37:33 UTC
433f364 fix stupid linting errors because trailing whitespace is the biggest single problem with tests ffs 25 October 2017, 14:29:47 UTC
0b47379 five font-synthesis tests 25 October 2017, 14:15:30 UTC
026f7ae some font-stretch ref tests 25 October 2017, 14:05:24 UTC
2f08c85 relax pass criteria to match wiggle room in spec 25 October 2017, 13:55:10 UTC
970d46e Rework mixed content tests. (#7938) * Rework mixed content tests. 1. The existing `iframe` and `form` tests both rely on `<iframe>` elements generating `error` events. That doesn't actually happen. This patch drops those tests; I'll rewrite them in a subsequent patch. 2. The test runner didn't properly wrap function calls with `step_func()`, which caused some errors to go unseen, as they weren't happening in the test's context. 3. Dropping audio and video samples to lowest common denominator types (wav and ogv) in the hopes of executing in a wider range of test harnesses. 4. Renamed the tests to lead with the type rather than the expected result, which makes it easier to find systemic issues like the above. Change-Id: Iab396d87150578f444039c425dbaa794298c38a7 Reviewed-on: https://chromium-review.googlesource.com/732116 Reviewed-by: Andy Paicu <andypaicu@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#510774} * fixup drop 'smallest.wav', as Firefox can't parse it. 25 October 2017, 13:54:23 UTC
63feac3 Add [SecureContext] attribute to SensorErrorEvent As it is specified at https://www.w3.org/TR/generic-sensor/#the-sensor-error-event-interface Change-Id: Icd4dbbf3a680d3542138d56821e740362cc5a5f0 Reviewed-on: https://chromium-review.googlesource.com/730008 Reviewed-by: Raphael Kubo da Costa (rakuco) <raphael.kubo.da.costa@intel.com> Reviewed-by: Alexander Shalamov <alexander.shalamov@intel.com> Commit-Queue: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com> Cr-Commit-Position: refs/heads/master@{#511422} 25 October 2017, 12:26:39 UTC
06ee473 Remove bare 'except' in Python. This fixes a flake8 error 25 October 2017, 07:42:56 UTC
35a8900 Add Web IDL tests for Wake Lock API (#7891) and create OWNERS file 25 October 2017, 03:04:42 UTC
d8f7898 Fix LayoutBox::AvailableLogicalHeightUsing() for positioned items This method was returning a wrong value for positioned items in combination with "box-sizing: border-box". The problem was that if the height of the element is given by its offset properties (top and bottom) we don't need to call AdjustContentBoxLogicalHeightForBoxSizing(). Created a test to verify that the problem is fixed using "height: -webkit-fill-available". Grid Layout is one of the places where AvailableLogicalHeight() is used, so this patch adds a new test for different cases based on grids. The test checks the combination of: positioned and non positioned elements, border-box and content-box, specific size and min-size. BUG=772512 TEST=fast/box-sizing/fill-available.html TEST=external/wpt/css/css-grid-1/grid-model/grid-box-sizing-001.html Change-Id: Ia5b943c6a3a2e33715fe9883edbbcdcae9d0c608 Reviewed-on: https://chromium-review.googlesource.com/735141 Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Reviewed-by: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Sergio Villar <svillar@igalia.com> Cr-Commit-Position: refs/heads/master@{#511271} 24 October 2017, 22:06:28 UTC
f506e30 Inherit referrer and policy when creating a nested browsing context BUG=763194 R=estark@chromium.org Change-Id: Ide3950269adf26ba221f573dfa088e95291ab676 Reviewed-on: https://chromium-review.googlesource.com/732652 Reviewed-by: Emily Stark <estark@chromium.org> Commit-Queue: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#511211} 24 October 2017, 18:47:28 UTC
09c7045 Fix wdspec tests using new_session fixture Tests are passing capabilities that should be used when creating the session, but they are passed directly as body of new session command, without adding them to a capabilities object. This is also ignoring all other configuration capabilities, preventing the browser from being launched in cases where the browser binary is passed to the driver as a capability. This patch adds a new fixture add_browser_capabilites, that is used by tests using new_session to provide the browser capabilities and optionally add others. 24 October 2017, 12:32:47 UTC
b164e05 [css-grid] Upstream fit-content() tests to WPT repository BUG=767015 Change-Id: Iceaeb7b6b1a3a5ed72ba1d7cc400086b478ebfc0 Reviewed-on: https://chromium-review.googlesource.com/730707 Reviewed-by: Javier Fernandez <jfernandez@igalia.com> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#511109} 24 October 2017, 12:30:06 UTC
354f583 Merge pull request #7963 from frivoal/ani-cursor [css-ui-3] Add missing flag 24 October 2017, 09:15:06 UTC
4c1ca0d [css-ui-3] Add missing flag The ANI format allowed but is not required by the spec, the test needs to be marked as optional. 24 October 2017, 08:59:23 UTC
b148f8e Make EME return a SecurityError when disabled by Feature Policy This changes the type of error returned to be a SecurityError, as discussed in https://github.com/w3c/encrypted-media/pull/432#pullrequestreview-68165178. This also makes 3 other small changes: 1) The deprecation warning is only shown when the feature is not enabled. 2) A separate console message is logged when a request has been rejected due to a Feature Policy in effect. 3) A UseCounter also counts the number of times that a request is rejected due to Feature Policy. Bug: 689802 Change-Id: Ic067fea9df858ba5390f74073e67a350043fe8ce Reviewed-on: https://chromium-review.googlesource.com/727319 Reviewed-by: Timothy Loh <timloh@chromium.org> Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Reviewed-by: David Dorwin <ddorwin@chromium.org> Commit-Queue: Raymes Khoury <raymes@chromium.org> Cr-Commit-Position: refs/heads/master@{#511051} 24 October 2017, 08:33:53 UTC
6f8c0ca Add a test for "keepalive" handling 24 October 2017, 06:28:46 UTC
a9dfc8e [import.meta.url] Implement import.meta.url behind flag (Blink-side) This CL implements https://html.spec.whatwg.org/#hostgetimportmetaproperties as HostGetImportMetaProperties() in V8Initializer.cpp and Modulator, and thus enables import.meta.url behind the flag added in https://chromium-review.googlesource.com/c/chromium/src/+/727179. This CL also adds a layout test, and sets up virtual test for that. Bug: 773713 Change-Id: I1d28123f803095535ed9a0208587e1dd873376cb Reviewed-on: https://chromium-review.googlesource.com/726525 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#510988} 24 October 2017, 01:42:03 UTC
0c76451 Revert "Revert "WPT tests for setRemoteDescription for adding and removing tracks."" This reverts commit 4e8a1ff7c4f07b2154a40f9ff50b418ecf6df0a9. Reason for revert: The original CL was reverted because the eventSequence keeping track of the order of ontrack firing and setRemoteDescription resolving was not modified when ontrack fired, rather upon a promise resolving that was resolved when ontrack fires. This added a delay and the order of promise then() callbacks became indeterminate. In this reland, ontrack has been modified to do eventSequence += 'ontrack;' instead. The original CL was reverted because of expecting: FAIL ontrack fires before setRemoteDescription resolves. assert_equals: expected "ontrack;setRemoteDescription;" but got "setRemoteDescription;ontrack;" But got: PASS ontrack fires before setRemoteDescription resolves. Original change's description: > Revert "WPT tests for setRemoteDescription for adding and removing tracks." > > This reverts commit 7224091bcdc52f1d9c7f6a8eecb3e7414f29aaeb. > > Reason for revert: causes tests failures on mac, e.g. https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests/builds/19421 > > May or may not be related to an unrelated revert that followed this original patch, https://chromium-review.googlesource.com/729719 > > Original change's description: > > WPT tests for setRemoteDescription for adding and removing tracks. > > > > These are behavior-driven tests, each test testing a specific behavior: > > - addTrack() with a track and no stream should fire ontrack with a > > remote track with the same ID and no streams. > > - addTrack() with a track and a stream should fire ontrack with a > > remote track and stream with matching IDs. > > - addTrack() with two tracks and a shared stream should fire ontrack > > twice with remote tracks and a shared remote stream, with matching > > IDs. > > - addTrack() with a track and two streams should fire ontrack with a > > track and two streams with matching IDs. > > - ontrack should fire before setRemoteDescription()'s promise resolves. > > - ontrack's receiver should match getReceivers(). > > - removeTrack() should not result in a receiver being removed. > > > > Unlike RTCPeerConnection-ontrack.https.html, these tests do not rely on > > transceiver support. When testing a behavior like "fires an event with > > a track" the test does not test unrelated things like the event being a > > complete implementation of RTCTrackEvent with transceivers and all. > > > > In a follow-up, I will add tests for other behavior associated with the > > removal of a track, including onmute events firing and the track being > > removed from the remote streams. > > > > Bug: 774303 > > Change-Id: I87d8a79d9e2e385610f749a9146b740cc649cf3f > > Reviewed-on: https://chromium-review.googlesource.com/719615 > > Commit-Queue: Henrik Boström <hbos@chromium.org> > > Reviewed-by: Taylor Brandstetter <deadbeef@chromium.org> > > Reviewed-by: Philip Jägenstedt <foolip@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#510241} > > TBR=hbos@chromium.org,deadbeef@chromium.org,foolip@chromium.org > > Change-Id: I8684d63e478a2ce63d760d9ec2a973b27f985729 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 774303 > Reviewed-on: https://chromium-review.googlesource.com/730723 > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#510404} TBR=hbos@chromium.org,deadbeef@chromium.org,foolip@chromium.org,mastiz@chromium.org Change-Id: I5f18c4426b9e39afbdf59537ad084c4ae461b54a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 774303 Reviewed-on: https://chromium-review.googlesource.com/731245 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#510858} 23 October 2017, 20:38:25 UTC
50d08dd Last(!!!!) step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - make blink-contrib folders contain valid tests that are not only programatically generated - get rid of the reliance on checkreport as much as possible in these tests This should unblock `checkreport` changes that break the upstream integration. Bug: 651742 Change-Id: Ia3f5f97ca3f6c26dd5abc857d8270bd58ed26a2c Reviewed-on: https://chromium-review.googlesource.com/730713 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#510809} 23 October 2017, 19:35:52 UTC
4978e20 Fix passing blobs on MessagePort and BroadcastChannel. Also add/update WPT tests to test this, and try to garbage collect the blob being send before the message is received. Bug: 740744, 351753 Change-Id: Ibe2f130dd3fa37130ceb0ed6330b5ba9282f9a7b Reviewed-on: https://chromium-review.googlesource.com/594495 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#510541} 23 October 2017, 17:06:29 UTC
37cf560 Add a README to acid/ 23 October 2017, 13:57:01 UTC
a2c528a Link to the Acid2 guide from Acid2 23 October 2017, 13:57:01 UTC
0e9ff8d Use the single upstream copy of Ahem 23 October 2017, 13:57:01 UTC
b9d2b6e Turn Acid3 into a reftest 23 October 2017, 13:57:01 UTC
3289b60 Add a reftest for Acid2 23 October 2017, 13:57:01 UTC
87c4206 Add Acid3 based on current copy at acid3.acidtests.org 23 October 2017, 13:57:01 UTC
c0bef78 Add Acid2 based on current copy at acid2.acidtests.org 23 October 2017, 13:57:01 UTC
9463de5 Merge pull request #7914 from rmcilroy/fix_raf Change callback-timeout-with-raf to use setTimeout. 23 October 2017, 12:35:23 UTC
300641b Upstream LayoutTests/html/dialog/* to WPT. Bug: 761790 Change-Id: I2ff688a24eb5faba6bdd5e6cd941c27275601f9f Reviewed-on: https://chromium-review.googlesource.com/722403 Commit-Queue: Shanmuga Pandi <shanmuga.m@samsung.com> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#510745} 23 October 2017, 10:41:58 UTC
0bc824a Merge pull request #7860 from w3c/MediaStreamTrack-idl Split MediaStreamTrack IDL tests into a separate file 23 October 2017, 10:35:37 UTC
39a0737 Fifth step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - make blink-contrib folders contain valid tests that are not only programatically generated - get rid of the reliance on checkreport as much as possible in these tests Bug: 651742 Change-Id: Ic5f9ae5c357d907cd4b88e2fd16c483254e3ac5a Reviewed-on: https://chromium-review.googlesource.com/730964 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#510734} 23 October 2017, 09:14:18 UTC
6048c3b Replace usage of setTimeout with step_timeout in html/infrastructure (#4974) This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. 22 October 2017, 22:47:01 UTC
9fbbe46 Replace usage of setTimeout with step_timeout in pointerevents (#4970) This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. 22 October 2017, 22:46:27 UTC
d90d873 Use assert_times_equal to compare 'progress' in iterationStart.html (#7902) As progress is computed from applying the animation effect's timing function, its output is unbounded and not necessary integer. See issue #7885 22 October 2017, 21:33:55 UTC
1de7a03 Add reference to a currently visual css3-color test (#7936) 22 October 2017, 19:03:18 UTC
eba1634 Change patch to just instantiate missing self.command_queue 22 October 2017, 18:36:09 UTC
a1f5367 [wptrunner] Guard against empty command_queue in BrowserManager.send_message This happens when sending the message 'init_failed' and causes wptrunne to hang. This patch is something I need to keep the tests running, but there is probably a cleaner solution. 22 October 2017, 18:36:09 UTC
1dfa574 Align 'IsPotentiallyTrustworthy' with the spec for `localhost`. This patch brings our treatment of localhost names into line with the secure contexts spec, which is ~safe enough to do since we're locking DNS resolution for `localhost` to loopback addresses as of https://chromium-review.googlesource.com/c/chromium/src/+/598068. This has a few impacts: * `http://*.localhost` subresources will not be treated as mixed content. * `http://*.localhost` top-level documents will be considered secure contexts. Intent to Ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/RC9dSw-O3fE/E3_0XaT0BAAJ Bug: 412058 Change-Id: I3df040e233ebb6c40f098bc45246415f63249451 Reviewed-on: https://chromium-review.googlesource.com/702277 Reviewed-by: Ryan Sleevi <rsleevi@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Emily Stark <estark@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#510678} 21 October 2017, 11:33:03 UTC
153e3fc Merge pull request #7921 from w3c/mediacapture-streams-OWNERS Add @eric-carlson to mediacapture-streams/OWNERS 21 October 2017, 07:36:52 UTC
091233a [css-grid] Take into account min size constrains for stretching auto tracks In r501249 we moved the stretch phase as the last step of the track sizing algorithm. However this introduced a regression as we were no longer taking into account the grid container min-width|height constraints during this step. The CSS WG modified the spec so it now defines what to do in these situations (https://drafts.csswg.org/css-grid/#algo-stretch): "If the free space is indefinite, but the grid container has a definite min-width/height, use that size to calculate the free space for this step instead." This patch adds a new method GridTrackSizingAlgorithmStrategy::FreeSpaceForStretchAutoTracksStep(). When we're in the DefiniteSizeStrategy it just returns the current free space. For the IndefiniteSizeStrategy it uses the min size of the grid container (respecting min-width|height properties) to calculate the free space. BUG=773625 TEST=external/wpt/css/css-grid-1/layout-algorithm/grid-stretch-respects-min-size-001.html Change-Id: I8864f9c5885e3caea534c4b69acd93ad28eb5bc9 Reviewed-on: https://chromium-review.googlesource.com/720918 Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Reviewed-by: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#510461} 20 October 2017, 17:29:22 UTC
9acb9b5 Revert "Fourth step of many to porting blink CSP tests to WPT" This reverts commit 3f04a6d75c5da9c2a53a6e59b934fe620aa8a9dd. Reason for revert: seems to have caused a leak: https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/11102 Original change's description: > Fourth step of many to porting blink CSP tests to WPT > > This has been a long time overdue but there are too many things currently > blocking on this so it's time to look at the blink-contrib folders. > > Goals are to: > - make blink-contrib folders contain valid tests that are not only > programatically generated > - get rid of the reliance on checkreport as much as possible in these tests > > Bug: 651742 > Change-Id: Ie2574838b953142cc2ee0011dff34b90546fbbe8 > Reviewed-on: https://chromium-review.googlesource.com/730384 > Commit-Queue: Andy Paicu <andypaicu@chromium.org> > Reviewed-by: Mike West <mkwst@chromium.org> > Cr-Commit-Position: refs/heads/master@{#510420} TBR=mkwst@chromium.org,andypaicu@chromium.org Change-Id: I417422a99eb30904d5527fe62e7d535a3a2b9786 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 651742 Reviewed-on: https://chromium-review.googlesource.com/731223 Reviewed-by: Sahel Sharifymoghaddam <sahel@chromium.org> Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#510442} 20 October 2017, 16:20:26 UTC
37f99dd Fix lint errors by replacing setTimeout with step_timeout 20 October 2017, 16:12:44 UTC
5726fd8 Add @eric-carlson to mediacapture-streams/OWNERS Per https://github.com/w3c/web-platform-tests/pull/7892#issuecomment-337947856 20 October 2017, 14:14:16 UTC
a1c0107 Fourth step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - make blink-contrib folders contain valid tests that are not only programatically generated - get rid of the reliance on checkreport as much as possible in these tests Bug: 651742 Change-Id: Ie2574838b953142cc2ee0011dff34b90546fbbe8 Reviewed-on: https://chromium-review.googlesource.com/730384 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#510420} 20 October 2017, 14:06:44 UTC
6d43e95 Merge pull request #7656 from lukebjerring/css-ref-test-linear-gradient Add ref test for linear gradient with transparent 20 October 2017, 13:51:11 UTC
c07a244 Revert "WPT tests for setRemoteDescription for adding and removing tracks." This reverts commit 7224091bcdc52f1d9c7f6a8eecb3e7414f29aaeb. Reason for revert: causes tests failures on mac, e.g. https://uberchromegw.corp.google.com/i/chromium.mac/builders/Mac10.11%20Tests/builds/19421 May or may not be related to an unrelated revert that followed this original patch, https://chromium-review.googlesource.com/729719 Original change's description: > WPT tests for setRemoteDescription for adding and removing tracks. > > These are behavior-driven tests, each test testing a specific behavior: > - addTrack() with a track and no stream should fire ontrack with a > remote track with the same ID and no streams. > - addTrack() with a track and a stream should fire ontrack with a > remote track and stream with matching IDs. > - addTrack() with two tracks and a shared stream should fire ontrack > twice with remote tracks and a shared remote stream, with matching > IDs. > - addTrack() with a track and two streams should fire ontrack with a > track and two streams with matching IDs. > - ontrack should fire before setRemoteDescription()'s promise resolves. > - ontrack's receiver should match getReceivers(). > - removeTrack() should not result in a receiver being removed. > > Unlike RTCPeerConnection-ontrack.https.html, these tests do not rely on > transceiver support. When testing a behavior like "fires an event with > a track" the test does not test unrelated things like the event being a > complete implementation of RTCTrackEvent with transceivers and all. > > In a follow-up, I will add tests for other behavior associated with the > removal of a track, including onmute events firing and the track being > removed from the remote streams. > > Bug: 774303 > Change-Id: I87d8a79d9e2e385610f749a9146b740cc649cf3f > Reviewed-on: https://chromium-review.googlesource.com/719615 > Commit-Queue: Henrik Boström <hbos@chromium.org> > Reviewed-by: Taylor Brandstetter <deadbeef@chromium.org> > Reviewed-by: Philip Jägenstedt <foolip@chromium.org> > Cr-Commit-Position: refs/heads/master@{#510241} TBR=hbos@chromium.org,deadbeef@chromium.org,foolip@chromium.org Change-Id: I8684d63e478a2ce63d760d9ec2a973b27f985729 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 774303 Reviewed-on: https://chromium-review.googlesource.com/730723 Reviewed-by: Mikel Astiz <mastiz@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#510404} 20 October 2017, 12:56:55 UTC
d8f68e0 Third step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - make blink-contrib folders contain valid tests that are not only programatically generated - get rid of the reliance on checkreport as much as possible in these tests Bug: 651742 Change-Id: I8ad66788ec28c01815437e71067c3ce9d4d54f7e Reviewed-on: https://chromium-review.googlesource.com/728159 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#510402} 20 October 2017, 12:03:53 UTC
9232047 Update html.idl and cssom-view.idl This updates the IDL to reflect the current state of HTML and CSSOM View. 20 October 2017, 11:47:56 UTC
8243e53 Second step of many to porting blink CSP tests to WPT This has been a long time overdue but there are too many things currently blocking on this so it's time to look at the blink-contrib folders. Goals are to: - make blink-contrib folders contain valid tests that are not only programatically generated - get rid of the reliance on checkreport as much as possible in these tests Bug: 651742 Change-Id: Iac30e9f4188e0cfdc47f0bb402807e97fb21831f Reviewed-on: https://chromium-review.googlesource.com/726080 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#510385} 20 October 2017, 09:40:39 UTC
back to top