Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
sort by:
Revision Author Date Message Commit Date
e263d32 Greg Whitworth 28 June 2017, 01:37:45 UTC Made more changes based on analysis of tests that were <= 5 tests to a given url hash in flex 25 January 2018, 18:37:11 UTC
edb4b84 Chris Nardi 25 January 2018, 06:15:16 UTC Support calc() in media queries calc() was previously unsupported in CSS media queries. This change adds in support for parsing calc() values in media queries, transitioning MediaQueryExp.cpp to use CSSParserHelpers functions instead of bare CSSParserTokens. Bug: 421909 Change-Id: I81fea4dc6c70caaab79874722f114d261c26c886 Reviewed-on: https://chromium-review.googlesource.com/884571 Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Chris Nardi <cnardi@chromium.org> Cr-Commit-Position: refs/heads/master@{#531825} 25 January 2018, 11:34:34 UTC
7c831ba Darren Shen 25 January 2018, 00:11:25 UTC [css-typed-om] Implement CSSNumericValue.type(). This patch implements CSSNumericValue.type(), which exposes the type of a CSSNumericValue in the form of a dictionary. We changed a lot of tests because we originally couldn't inspect the type of a CSSNumericValue via JavaScript, so we mainly wrote unit tests. Now we can directly test the types in web platform tests. WIP API: https://github.com/w3c/css-houdini-drafts/pull/546/files Bug: 803684 Change-Id: Ie86a81c42cab34cd01286a3066be6bc9fda50fce Reviewed-on: https://chromium-review.googlesource.com/880422 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#531751} 25 January 2018, 11:27:20 UTC
58d769a Rakina Zata Amni 25 January 2018, 07:42:26 UTC Revert "Revert "Fix retargeting of result in elementFromPoint and elementsFromPoint"" crrev.com/c/808446 is reverted because of failure in ASAN Buildbot Revert CL Link: crrev.com/c/880264 Failure link: https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20ASAN/builds/8618 The failure is accessing *target_ancestor_iterator when it is out of bounds. Link: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/TreeScope.cpp?q=Treescope.cpp&sq=package:chromium&rcl=dd944882a245a5117b50cb417138d92f32d931d6&l=393 as there were no bound checks for target_ancestor_iterator. It wasn't caught by layout tests because it's still returning the correct results, because it doesn't crash when getting *target_ancestor_iterator when it's out of bound. It just stops the while-loop and returned at https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/TreeScope.cpp?q=Treescope.cpp&sq=package:chromium&rcl=dd944882a245a5117b50cb417138d92f32d931d6&l=398 Also, since the ASAN buildbot is not done before the CL is merged, this wasn't caught by trybots prior to committing. The fix is just adding a bound check for target_ancestor_riterator here: https://chromium-review.googlesource.com/c/chromium/src/+/880741/2..3/third_party/WebKit/Source/core/dom/TreeScope.cpp I have confirmed by using ASAN locally that it is fixed now. Before the fix, running the failing tests with ASAN build fails. Bug: 759947,805039 Change-Id: I9934af8131f285045e0eb80923f190b6d88cef7d Reviewed-on: https://chromium-review.googlesource.com/880741 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#531839} 25 January 2018, 07:50:54 UTC
dadaf1a Luna Lu 24 January 2018, 22:10:41 UTC Add WPT tests for feature policy 1. Added tests for header policy. a. document.policy shows correctly parsed policy b. local / remote iframes without allow attribute correctly inherit document.policy c. dynamically update allow attribute updates the policy correctly. 2. Added tests for nested policies. Bug: 732003 Change-Id: I869449f6bba89fc58997355df27249f403d76808 Reviewed-on: https://chromium-review.googlesource.com/796952 Commit-Queue: Luna Lu <loonybear@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#531698} 24 January 2018, 23:14:12 UTC
c522284 Ian Kilpatrick 24 January 2018, 21:20:13 UTC Create new top-level dir, OWNERS for CSS Layout API (#9183) This is for being able to write web-platform-tests for the CSS Layout API[1] [1] https://drafts.css-houdini.org/css-layout-api/ 24 January 2018, 21:20:13 UTC
357c23f Geoffrey Sneddon 23 January 2018, 23:42:08 UTC Fix #9169: test_main_with_args in tools/lint has wrong expectation This got broken by 19c79185c1d4978aeb7191494541711ca4f3a582 24 January 2018, 17:14:16 UTC
e58fa6e Geoffrey Sneddon 23 January 2018, 23:12:07 UTC Forward arguments to pytest in tools/tox.ini 24 January 2018, 17:14:16 UTC
91d6ac9 Yutaka Hirano 24 January 2018, 14:52:05 UTC [SendBeacon] Verify that the quota will recover after fetching Bug: 695939, 805348 Change-Id: I6c0e1643b70a94e37261ef709d58da13fa9b6cdd Reviewed-on: https://chromium-review.googlesource.com/883063 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> Cr-Commit-Position: refs/heads/master@{#531524} 24 January 2018, 15:03:23 UTC
ae4da80 Philip Jägenstedt 24 January 2018, 12:04:03 UTC Add missing untested IDL for MediaStream tests The cryptic failures in https://github.com/w3c/web-platform-tests/issues/8112 are because of this. (That issue is about fixing the failure mode.) 24 January 2018, 13:10:43 UTC
b32cfc9 Andy Paicu 24 January 2018, 11:51:03 UTC Fixed race condition in test report-uri-from-child-frame Bug: 694525 Change-Id: I444672b14210213d00b644a91e63709bd602874e Reviewed-on: https://chromium-review.googlesource.com/883281 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#531500} 24 January 2018, 12:20:23 UTC
9cdea02 Andy Paicu 17 January 2018, 15:01:54 UTC Fixed wpt csp reporting tests and moved over chrome internal ones Bug: 694525,802188 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I34cca4afc854ffb4f02fc705c4f6293fdc0d51e7 Reviewed-on: https://chromium-review.googlesource.com/552640 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#529668} 24 January 2018, 11:21:36 UTC
c992d86 Takayoshi Kochi 24 January 2018, 10:47:13 UTC Revert "Remove UA shadow usage from ImageDocument." Reverts "Remove UA shadow usage from ImageDocument." https://chromium-review.googlesource.com/877693 After more investigation, the removal turned out violating the HTML spec. The corresponding HTML spec: https://html.spec.whatwg.org/multipage/browsing-the-web.html#read-media mandates <body> for the ImageDocument must have only one <img> element. The previous change introduced intermediate container <div> element, but it is not conforming to the spec. Originally the UA shadow was attached to <body> and hides the container and this CL restores the behavior. Added a WPT test for checking the case. There was an existing test case for this, but when ImageDocument is embedded in an <iframe>, the new media-like view isn't enabled and no UA shadow is used. The new test creates a popup window which is a shrinkable container, and Blink's UA shadow implementation is used. Other UA implementation may benefit from this (or may not, but at least do not do harm). Bug: 802185 Change-Id: Ifac013eced8f1d234092acffb726a90c03f988f9 Reviewed-on: https://chromium-review.googlesource.com/882630 Commit-Queue: Takayoshi Kochi <kochi@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#531494} 24 January 2018, 10:55:45 UTC
d032fb2 TAMURA, Kent 24 January 2018, 09:49:22 UTC custom-elements: Add a test for customized built-in elements coverage. (#9175) 24 January 2018, 09:49:22 UTC
dde12fa Geoffrey Sneddon 24 January 2018, 09:47:15 UTC Add a testharness.js wrapper for Acid3 (#8815) This allows us to track individual subtests and their results, rather than simply a PASS/FAIL result for the entirety of Acid3. 24 January 2018, 09:47:15 UTC
0e28b06 Matt Falkenhagen 24 January 2018, 03:53:06 UTC S13nServiceWorker: Support network fallback with blob request body. For subresource requests only. This makes a clone of the request body before passing it to the service worker in ServiceWorkerSubresourceLoader. This way if the service worker does network fallback, the request can be passed to network with the request body intact. Change-Id: I00c1861449e997a50c417336961a7c8c62bc710e Bug: 778878 Reviewed-on: https://chromium-review.googlesource.com/867817 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#531414} 24 January 2018, 04:03:19 UTC
4736272 Geoffrey Sneddon 24 January 2018, 00:48:41 UTC Make all copies of 100x100-green.png identical This gets rid of the CSS-COLLIDING-SUPPORT-NAME failure on master from 1f69b4225e6c424b85b7a90b3851a72bf8915b60 (see https://github.com/w3c/web-platform-tests/issues/9171 for how that landed) 24 January 2018, 03:01:03 UTC
4aede5c Harald Alvestrand 24 January 2018, 00:02:52 UTC Fix issues in RTCStats-helper.js for WPT Make a number of stats optional because their generation depends on specific states; they're not always present. Check a number of stats only if the kind is the right one. Bug: None Change-Id: I7f3e307b0f0f14df0f62bc2ac3a226018640f873 Reviewed-on: https://chromium-review.googlesource.com/880983 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#531386} 24 January 2018, 00:32:57 UTC
7d14800 Chris Cunningham 23 January 2018, 22:53:09 UTC Delete ancient media canPlayType tests, update WPT version. The deleted tests are covered by the remaining wpt/html/semantics/embedded-content/media-elements/mime-types/canPlayType.html TEST: Pass canPlayType.html WPT test. Change-Id: I888c725194ae9fd4007e140f07f0639eb69495c1 Reviewed-on: https://chromium-review.googlesource.com/879138 Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#531371} 23 January 2018, 23:16:28 UTC
cf8ec6b Manuel Rego Casasnovas 23 January 2018, 21:46:46 UTC [css-multicol] Support percentages in column-gap This patch adds percentage support to column-gap property. Most of the changes are related to the parsing logic, the column-gap property now accepts both length and percentages, on top of the "normal" initial value. A new utility class GapLength has been added, as it'll be useful to implement row-gap in the future. Apart from that the muticolumn layout code has been modified to resolve the percentage gaps (treating them as zero while computing preferred widths) and resolving them during layout. This doesn't follow the current text on the spec, but there is an ongoing discussion that might cause the text is changed: https://github.com/w3c/csswg-drafts/issues/509#issuecomment-355242101 We could update the implementation once we have a definitive answer from the CSS WG. Added a new WPT test to check the behavior under different sizing conditions. BUG=799413 TEST=external/wpt/css/css-multicol/multicol-gap-percentage-001.html Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Icccd046e913353b6f525481046a41ad125aea5ff Reviewed-on: https://chromium-review.googlesource.com/878199 Reviewed-by: meade_(do not use) <meade@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#531356} 23 January 2018, 21:58:14 UTC
a289ff1 Morten Stenshorne 23 January 2018, 20:24:12 UTC Fix and enable as many external/wpt/css/CSS2/ tests as possible. A few were skipped for no reason. Some of them turned out to pass, while others fail. Then there were quite a few manual tests, and those we still need to skip. Made some (mostly minor) changes to some of the tests to make them pass. They were making invalid assumptions about fonts (glyphs with unexpected negative bearing, kerning, etc.) and line heights. One test was also assuming that painting the same glyph multiple times would produce the exact same result as painting it just once, but that's not necessarily true for anti-aliasing. It was pretty hard to figure out what floats-clear/floats-028-ref.xht was about (old IE bug fixed?), but I made the ref more similar to the test, so that we don't make assumptions about line height. Also updated expectations for LayoutNG, because it turned out that more more of these tests pass there. Bug: 711704, 711709, 711805, 711807 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I6e34e037852ef31cfe8d85688865823d6f9d2d0a Reviewed-on: https://chromium-review.googlesource.com/873310 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#531322} 23 January 2018, 20:34:23 UTC
aebdeed Xida Chen 23 January 2018, 18:59:02 UTC Make some css-paint-api/ tests fail on browsers that don't support PaintWorklet Right now there are a few tests under external/wpt/css-paint-api/ that pass no matter whether a browser supports PaintWorklet or not. The list of these tests are here: http://wpt.fyi/css-paint-api This CL corrects those tests and make them fail on browsers that don't support PaintWorklet. This CL also does a null check for the document paint definition, the null check is exercised in parse-input-arguments-018.https.html. Bug: 768683 Change-Id: Ic58daf8c34505f02c1c5588120a17d8476a15536 Reviewed-on: https://chromium-review.googlesource.com/711381 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#531290} 23 January 2018, 19:12:29 UTC
2e19bfd jgraham 23 January 2018, 15:47:18 UTC Merge pull request #9167 from w3c/sync_5bdd1e0708424bff053da8128699b7c613db91b9 Use assert_times_equal for comparing timing values. 23 January 2018, 15:47:18 UTC
398fc2f jgraham 23 January 2018, 15:46:56 UTC Merge pull request #9166 from w3c/sync_094b08065aed473a82b787d42e4d5fc6fa9e7954 Double epsilon value for assert_times_equal. 23 January 2018, 15:46:56 UTC
f9917a5 jgraham 23 January 2018, 15:46:39 UTC Merge pull request #9165 from w3c/sync_da70788987d9f8dfadad37e0144190502a669c51 Introduce assert_time_equals_literal and use it. 23 January 2018, 15:46:39 UTC
9dad718 jgraham 23 January 2018, 15:46:21 UTC Merge pull request #9164 from w3c/sync_e5f362229b22a1c70f7d9b10b5d32cbcc64c1509 Tests for calc() on font-size on various situations. 23 January 2018, 15:46:21 UTC
2be0862 jgraham 23 January 2018, 15:46:01 UTC Merge pull request #9163 from w3c/sync_f5490e89b90a7f5cdeb0e3c2e74e96d49344cbe3 Add [SecureContext] to navigator.credentials 23 January 2018, 15:46:01 UTC
070555b jgraham 23 January 2018, 15:45:42 UTC Merge pull request #9162 from w3c/sync_72f8f50aa1b630e27793680455e54608ec21816a Fix slotted invalidation. 23 January 2018, 15:45:42 UTC
d88a850 jgraham 23 January 2018, 15:45:25 UTC Merge pull request #9161 from w3c/sync_1babdff141ece20e5b1bda7d25140d7b8106b3dc Add validity state check for WebDriver:ElementClear. 23 January 2018, 15:45:25 UTC
87e3733 jgraham 23 January 2018, 15:45:04 UTC Merge pull request #9160 from w3c/sync_d4888ba9f7936f00dd672f8f36bc222ddaa1eab2 Fix attributeChangedCallback isn't fired with correct newValue when the attribute value is an empty string; 23 January 2018, 15:45:04 UTC
3e810d2 jgraham 23 January 2018, 15:44:46 UTC Merge pull request #9159 from w3c/sync_64b9832958e2cda4c040ef6c65d66ed9239ed183 Accept null for body param in constructor of Response. 23 January 2018, 15:44:46 UTC
73e945e jgraham 23 January 2018, 15:44:28 UTC Merge pull request #9158 from w3c/sync_b56eb26e2028d4146db9b42d9cb21326161e281a Don't allow fallback alignment in place-content shorthand. r=xidorn,mats 23 January 2018, 15:44:28 UTC
4922902 jgraham 23 January 2018, 15:44:09 UTC Merge pull request #9157 from w3c/sync_87d0ca06e4391c2860eb9330ed6aa4735a304f52 Add WPT test for the attributeChangedCallback which is triggered from parser; 23 January 2018, 15:44:09 UTC
81bc633 jgraham 23 January 2018, 15:43:50 UTC Merge pull request #9156 from w3c/sync_8c1099cb757bf950b9b5b375df77eb65e7ff365e Make WebDriver:ElementClear conforming to standard. 23 January 2018, 15:43:50 UTC
b97906b jgraham 23 January 2018, 15:43:32 UTC Merge pull request #9155 from w3c/sync_0e2973ecb01cb4f6dd4e5cecf28ccb3f98551c2f Make composite member of Keyframe dictionary objects accept null values; 23 January 2018, 15:43:32 UTC
1e4e941 jgraham 23 January 2018, 15:43:14 UTC Merge pull request #9154 from w3c/sync_339616f46ab0b32256936b3a77d85186a6e85d6c Remove obsolete optional parameter `reset_session_id` from `delete_session`. 23 January 2018, 15:43:14 UTC
72c7514 jgraham 23 January 2018, 15:42:54 UTC Merge pull request #9153 from w3c/sync_0133203932cba221edacc57e91155f8a3e8bc59a Use classic pytest output style for WPT. r=davehunt,jgraham 23 January 2018, 15:42:54 UTC
9224ea9 jgraham 23 January 2018, 15:42:36 UTC Merge pull request #9152 from w3c/sync_cd89b4fdc186d5dd8965cea6dcba18a7fe633a1f Stop toggling selectedness state of <option disabled>. 23 January 2018, 15:42:36 UTC
052dbc6 jgraham 23 January 2018, 15:42:18 UTC Merge pull request #9151 from w3c/sync_86ff16217cf23ff4580e263b302b475b28bd5422 P2 Make about-blank-replacement.https.html check simple about:blank and about:srcdoc cases. 23 January 2018, 15:42:18 UTC
4c9cf37 jgraham 23 January 2018, 15:41:59 UTC Merge pull request #9150 from w3c/sync_9d9eadd6a42160935a966bd2f39b5cdecf945997 Fix http status test to return in the right places, 23 January 2018, 15:41:59 UTC
0358955 jgraham 23 January 2018, 15:41:42 UTC Merge pull request #9149 from w3c/sync_af4895ab8c8fcea44e7a1cc6453f54ffb985908b Try GoToAnchor() with unescaped string before using document's charset. 23 January 2018, 15:41:42 UTC
6e2eb8e jgraham 23 January 2018, 15:41:25 UTC Merge pull request #9148 from w3c/sync_b366abd65496bfa924c0dac4c5279c05a7c27d0d P1: Update the wpt tests to expect to reject the cors synthesized response to a same origin request. 23 January 2018, 15:41:25 UTC
51907f3 jgraham 23 January 2018, 15:41:07 UTC Merge pull request #9147 from w3c/sync_e8f83adeba1dfbd29993ec09f5e04a52afb3ca4f Fix incorrect custom element type in CustomElementData. f=echen, 23 January 2018, 15:41:07 UTC
8c8a887 jgraham 23 January 2018, 15:40:48 UTC Merge pull request #9146 from w3c/sync_146ad6458647d0ea0f84cbba40edbd194f67407a Add a test for execution order of inline async module scripts 23 January 2018, 15:40:48 UTC
a9d2142 jgraham 23 January 2018, 15:40:31 UTC Merge pull request #9145 from w3c/sync_19c79185c1d4978aeb7191494541711ca4f3a582 Preprocess wpt lint paths to be relative to the wpt root 23 January 2018, 15:40:31 UTC
d20aca0 jgraham 23 January 2018, 15:40:14 UTC Merge pull request #9144 from w3c/sync_24f3c1e258e280c88a521b6b2b6e6048017005de css-display] Update display: contents on Unusual Elements to the spec. 23 January 2018, 15:40:14 UTC
2e6e104 jgraham 23 January 2018, 15:39:53 UTC Merge pull request #9143 from w3c/sync_8ae93d725dd36b3ab7ea0b70f345b5b4684e98ab P8 Fix unregister-then-register-new-script.https.html to not race iframe.remove() and expect resurrection on failed scripts. 23 January 2018, 15:39:53 UTC
24c269e jgraham 23 January 2018, 15:39:35 UTC Merge pull request #9142 from w3c/sync_7a48a49b34d59657076e65fe22523a6e9c84cf5c css-ui] Add a 'text-overflow' web platform test. 23 January 2018, 15:39:35 UTC
7a06985 jgraham 23 January 2018, 15:39:18 UTC Merge pull request #9141 from w3c/sync_e86f0f89ff52e0bceca69a228ed4a6adfaf3b705 css-ui] Skip anonymous boxes (rather than all pseudos) when looking for the 'overflow' style frame. 23 January 2018, 15:39:18 UTC
c190ce0 jgraham 23 January 2018, 15:38:58 UTC Merge pull request #9140 from w3c/sync_53bca18327e874eb70a12d839f9ddd8bd1427c69 Safely shutdown Firefox from in delete_session. 23 January 2018, 15:38:58 UTC
ad848a0 jgraham 23 January 2018, 15:38:40 UTC Merge pull request #9139 from w3c/sync_dd7e676471936524dd0f20549d0dfe21fc0851f7 Fix test that didn't take account of module scripts' defer scheduling 23 January 2018, 15:38:40 UTC
d878f0f jgraham 23 January 2018, 15:33:52 UTC Merge pull request #9138 from w3c/sync_401b9141bfe60cea9fadc629cc1053085fae46a3 Handle errors for inline module scripts and ensure we update the module map after fetch errors 23 January 2018, 15:33:52 UTC
5bdd1e0 Hiroyuki Ikezoe 23 January 2018, 15:27:59 UTC Use assert_times_equal for comparing timing values. MozReview-Commit-ID: CUn1f8M0jo5 Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430654 [ci skip] 23 January 2018, 15:33:13 UTC
094b080 Hiroyuki Ikezoe 23 January 2018, 15:27:58 UTC Double epsilon value for assert_times_equal. Since the function assumes that both of actual and expected values have the same precision requirements. MozReview-Commit-ID: 4C3TAH6mUVg Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430654 [ci skip] 23 January 2018, 15:33:12 UTC
da70788 Hiroyuki Ikezoe 23 January 2018, 15:27:58 UTC Introduce assert_time_equals_literal and use it. This assertion is supposed to be used where the first argument has a tolerance but the second argument doesn't have such tolerance. Whereas assert_times_equal() is supposed to be used for the case both arguments have the same tolerance, actually it hasn't, it will be fixed in a subsequent patch in this patch series. MozReview-Commit-ID: FEDHilbX2rm Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430654 [ci skip] 23 January 2018, 15:33:12 UTC
e5f3622 Emilio Cobos Álvarez 23 January 2018, 15:27:57 UTC Tests for calc() on font-size on various situations. It makes no sense to pass a custom base size of zero in presence of rem, ex, or ch units. MozReview-Commit-ID: 7ZZwRzQKREX Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1431031 [ci skip] 23 January 2018, 15:33:12 UTC
f5490e8 J.C. Jones 23 January 2018, 15:27:57 UTC Add [SecureContext] to navigator.credentials It was neglected to mark navigator.credentials as [SecureContext], yet it must be for spec compliance and powerful-features compliance. MozReview-Commit-ID: BYKGqqhoS2L Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430947 [ci skip] 23 January 2018, 15:33:12 UTC
1babdff Andreas Tolfsen 23 January 2018, 15:27:56 UTC Add validity state check for WebDriver:ElementClear. This patch checks that the element satisfies its form control constraints, as well as being empty, before deciding not to clear the element. This will make it possible to clear elements that have invalid input. The "clear a resettable element" algorithm is missing a check of the <input> element's ValidityState. WebDriver:ElementClear has a subtle bug that only manifests in Gecko because Blink rejects invalid key input to validation fields such as <input type=number>, but Gecko does not. The value property of <input type=number> will not be updated unless the input is actually valid, which means the first step of the algorithm will pass irregardless of whether the user has actually modified it. MozReview-Commit-ID: C2M3Fl1iKx6 Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430575 [ci skip] 23 January 2018, 15:33:11 UTC
72f8f50 Emilio Cobos Álvarez 23 January 2018, 15:27:56 UTC Fix slotted invalidation. This is a partial revert of https://github.com/servo/servo/commit/ce1d8cd232dfbc9e0a52f9467ba2bc209087ea63 If you're in a shadow tree, you may not be slotted but you still need to look at the slotted rules, since a <slot> could be a descendant of yours. Just use the same invalidation map everywhere, and remove complexity. This means that we can do some extra work while trying to gather invalidation if there are slotted rules, but I don't think it's a problem. The test is ported from https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/css/invalidation/slotted.html?l=1&rcl=58d68fdf783d7edde1c82a642e037464861f2787 Curiously, Blink fails the test as written, presumably because they don't flush styles from getComputedStyle correctly (in their test they do via updateStyleAndReturnAffectedElementCount), due to <slot>s not being in the flat tree in their implementation. MozReview-Commit-ID: 6b7BQ6bGMgd Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429846 [ci skip] 23 January 2018, 15:33:11 UTC
d4888ba Edgar Chen 23 January 2018, 15:27:55 UTC Fix attributeChangedCallback isn't fired with correct newValue when the attribute value is an empty string; MozReview-Commit-ID: L3RvNPNDfUC Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430034 [ci skip] 23 January 2018, 15:33:11 UTC
64b9832 Xidorn Quan 23 January 2018, 15:27:55 UTC Accept null for body param in constructor of Response. MozReview-Commit-ID: LeEFcQzPJlv Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1303025 [ci skip] 23 January 2018, 15:33:10 UTC
87d0ca0 Edgar Chen 23 January 2018, 15:27:54 UTC Add WPT test for the attributeChangedCallback which is triggered from parser; MozReview-Commit-ID: G0Cnxmv3sP8 Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1425079 [ci skip] 23 January 2018, 15:33:10 UTC
8c1099c Andreas Tolfsen 23 January 2018, 15:27:53 UTC Make WebDriver:ElementClear conforming to standard. This implements the remote end steps for the Element Clear command from WebDriver in Marionette. The WPT test webdriver/tests/interaction/element_clear.py was deleted because it tested a previous definition of the Element Clear command and many of its tests were either incorrect or replaced by the new tests. MozReview-Commit-ID: C2xmIlhSAdW Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1354211 [ci skip] 23 January 2018, 15:33:10 UTC
b56eb26 Emilio Cobos Álvarez 23 January 2018, 15:27:54 UTC Don't allow fallback alignment in place-content shorthand. r=xidorn,mats MozReview-Commit-ID: sALBFJeqvr Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1430622 [ci skip] 23 January 2018, 15:33:10 UTC
0133203 Andreas Tolfsen 23 January 2018, 15:27:51 UTC Use classic pytest output style for WPT. r=davehunt,jgraham The upstream upgrade of pytest came with a new test progress percentage feature that introduced a lot of unnecessary log output in WPT wdspec tests. This adds a pytest flag that reverts it to use the "classic" output style, which does not have a test progress bar. MozReview-Commit-ID: 9ucB7CzV5ig Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429388 [ci skip] 23 January 2018, 15:33:09 UTC
0e2973e Brian Birtles 23 January 2018, 15:27:53 UTC Make composite member of Keyframe dictionary objects accept null values; This patch reflects the following change to the Web Animations spec: https://github.com/w3c/csswg-drafts/commit/abf76745b50c8943e8b16c13abc61cb6ca814830 MozReview-Commit-ID: A2GD1igUf5f Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429671 [ci skip] 23 January 2018, 15:33:09 UTC
339616f Henrik Skupin 23 January 2018, 15:27:52 UTC Remove obsolete optional parameter `reset_session_id` from `delete_session`. By calling "delete_session" the currently used session id always has to be reset, because each session has its own unique id. MozReview-Commit-ID: H9RiuNj7fRd Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429562 [ci skip] 23 January 2018, 15:33:09 UTC
86ff162 Ben Kelly 23 January 2018, 15:27:50 UTC P2 Make about-blank-replacement.https.html check simple about:blank and about:srcdoc cases. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1426979 [ci skip] 23 January 2018, 15:33:08 UTC
9d9eadd James Graham 23 January 2018, 15:27:49 UTC Fix http status test to return in the right places, This was a regression from bug 1396534 MozReview-Commit-ID: 9Yfdo2rGqVZ Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429045 [ci skip] 23 January 2018, 15:33:08 UTC
cd89b4f Andreas Tolfsen 23 January 2018, 15:27:51 UTC Stop toggling selectedness state of <option disabled>. When WebDriver:ElementClick clicks an <option disabled> element, its selectedness state should according to a new specification change proposed not change: https://github.com/w3c/webdriver/pull/1189 This patch provides tests for the specification change. MozReview-Commit-ID: EXG98LjgB7d Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1429384 [ci skip] 23 January 2018, 15:33:08 UTC
af4895a Alphan Chen 23 January 2018, 15:27:48 UTC Try GoToAnchor() with unescaped string before using document's charset. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1421214 [ci skip] 23 January 2018, 15:33:06 UTC
b366abd Tom Tung 23 January 2018, 15:27:47 UTC P1: Update the wpt tests to expect to reject the cors synthesized response to a same origin request. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1427978 [ci skip] 23 January 2018, 15:33:06 UTC
e8f83ad John Dai 23 January 2018, 15:27:47 UTC Fix incorrect custom element type in CustomElementData. f=echen, Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1419662 [ci skip] 23 January 2018, 15:33:06 UTC
146ad64 Jon Coppeard 23 January 2018, 15:27:46 UTC Add a test for execution order of inline async module scripts Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1361369 [ci skip] 23 January 2018, 15:33:05 UTC
19c7918 Geoffrey Sneddon 23 January 2018, 15:27:46 UTC Preprocess wpt lint paths to be relative to the wpt root MozReview-Commit-ID: EUS7sjPhWoH Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1428582 [ci skip] 23 January 2018, 15:33:05 UTC
24f3c1e Emilio Cobos Álvarez 23 January 2018, 15:27:45 UTC css-display] Update display: contents on Unusual Elements to the spec. This will pass[1] whenever the next WPT sync happens. See: https://drafts.csswg.org/css-display/#unbox-html [1]: https://github.com/w3c/web-platform-tests/blob/master/css/css-display/display-contents-unusual-html-elements-none.html MozReview-Commit-ID: 19dqDSxVm7A Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1427292 [ci skip] 23 January 2018, 15:33:05 UTC
8ae93d7 Ben Kelly 23 January 2018, 15:27:44 UTC P8 Fix unregister-then-register-new-script.https.html to not race iframe.remove() and expect resurrection on failed scripts. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1425975 [ci skip] 23 January 2018, 15:33:05 UTC
53bca18 Henrik Skupin 23 January 2018, 15:27:43 UTC Safely shutdown Firefox from in delete_session. With the request to shutdown the browser, a given amount of time has to be waited to allow the process to shutdown itself. Only if the process is still running afterward it has to be killed. Firefox has an integrated background monitor which observes long running threads during shutdown, and kills those after 65s. To allow Firefox to shutdown on its own, geckodriver has to wait that time, and some additional seconds. MozReview-Commit-ID: 4LRLQE0jZzw Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1403923 [ci skip] 23 January 2018, 15:33:04 UTC
7a48a49 Mats Palmgren 23 January 2018, 15:27:44 UTC css-ui] Add a 'text-overflow' web platform test. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1403986 [ci skip] 23 January 2018, 15:33:04 UTC
dd7e676 Jon Coppeard 23 January 2018, 15:27:42 UTC Fix test that didn't take account of module scripts' defer scheduling Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1426642 [ci skip] 23 January 2018, 15:33:04 UTC
e86f0f8 Mats Palmgren 23 January 2018, 15:27:43 UTC css-ui] Skip anonymous boxes (rather than all pseudos) when looking for the 'overflow' style frame. Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1343980 [ci skip] 23 January 2018, 15:33:04 UTC
401b914 Jon Coppeard 23 January 2018, 15:27:41 UTC Handle errors for inline module scripts and ensure we update the module map after fetch errors Upstreamed from https://bugzilla.mozilla.org/show_bug.cgi?id=1426140 [ci skip] 23 January 2018, 15:33:03 UTC
9c8964b Bhagirathi Satpathy 23 January 2018, 12:17:09 UTC MessageEvent initMessageEvent should throw error in case of no argument MessageEvent initMessageEvent method should throw NotEnoughArguments error in case of no argument. Bug: Change-Id: I522f120456db3e30b4aa2f83144871fbe58e27fc Reviewed-on: https://chromium-review.googlesource.com/880263 Commit-Queue: Bhagirathi Satpathy <bhagirathi.s@samsung.com> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#531209} 23 January 2018, 12:26:38 UTC
14017b1 Wanming Lin 23 January 2018, 08:28:59 UTC Merge pull request #9131 from kaixinjxq/proximity_common Add Proximity Sensor tests and delete outdated tests 23 January 2018, 08:28:59 UTC
59e8791 Takashi Sakamoto 23 January 2018, 08:14:05 UTC Revert "Fix retargeting of result in elementFromPoint and elementsFromPoint" This reverts commit dd944882a245a5117b50cb417138d92f32d931d6. Reason for revert: This causes WebKit Linux Trusty ASAN buildbot failure. https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20ASAN/builds/8618 23:46:29.565 3877 ==1==ERROR: AddressSanitizer: use-after-poison on address 0x7ead60c0dbf0 at pc 0x00000dca937a bp 0x7ffd86b90c10 sp 0x7ffd86b90c08 23:46:29.565 3877 READ of size 8 at 0x7ead60c0dbf0 thread T0 (content_shell) 23:46:29.565 3877 #0 0xdca9379 in operator==<const blink::TreeScope, const blink::TreeScope> third_party/WebKit/Source/platform/heap/Member.h:128:27 23:46:29.565 3877 #1 0xdca9379 in blink::TreeScope::Retarget(blink::Element const&) const third_party/WebKit/Source/core/dom/TreeScope.cpp:393:0 23:46:29.565 3877 #2 0xdca8894 in blink::TreeScope::HitTestPointInternal(blink::Node*) const third_party/WebKit/Source/core/dom/TreeScope.cpp:267:10 23:46:29.565 3877 #3 0xdca8325 in HitTestPoint third_party/WebKit/Source/core/dom/TreeScope.cpp:254:10 23:46:29.566 3877 #4 0xdca8325 in blink::TreeScope::ElementFromPoint(double, double) const third_party/WebKit/Source/core/dom/TreeScope.cpp:245:0 23:46:29.566 3877 #5 0xc9353a7 in elementFromPoint third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h:38:23 Original change's description: > Fix retargeting of result in elementFromPoint and elementsFromPoint > > Currently elementFromPoint and elementsFromPoint are not per spec, and it may > return null incorrectly. This change adds retargeting of the result with > respect to the context object, and adds some tests that are similar to > elementFromPoint tests in WebKit, but with some corrected cases: > https://git.webkit.org/?p=WebKit-https.git;a=blob;f=LayoutTests/fast/shadow-dom/DocumentOrShadowRoot-prototype-elementFromPoint.html;h=a8dc4da2430713521b9ba77c742db10397a8e638;hb=HEAD > > Spec: > https://w3c.github.io/webcomponents/spec/shadow/#extensions-to-the-documentorshadowroot-mixin > > Bug: 759947 > Change-Id: I6aece5e9cc826124772c6ce13c806865055b2b9b > Reviewed-on: https://chromium-review.googlesource.com/808446 > Commit-Queue: Rakina Zata Amni <rakina@chromium.org> > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Reviewed-by: Hayato Ito <hayato@chromium.org> > Reviewed-by: Takayoshi Kochi <kochi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#531139} TBR=kochi@chromium.org,dgozman@chromium.org,hayato@chromium.org,pfeldman@chromium.org,rakina@chromium.org Change-Id: Id62abd371d93627d3178b63ca189cecfe9ff44d4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 759947 Reviewed-on: https://chromium-review.googlesource.com/880264 Reviewed-by: Takashi Sakamoto <tasak@google.com> Commit-Queue: Takashi Sakamoto <tasak@google.com> Cr-Commit-Position: refs/heads/master@{#531178} 23 January 2018, 08:24:07 UTC
6356b9e kaixinjxq 23 January 2018, 05:50:43 UTC Add Proximity Sensor tests and delete outdated tests 23 January 2018, 05:57:36 UTC
34a8c8a Ovidio Henriquez 19 January 2018, 19:43:00 UTC Add RemoveFakeService to BT test interface This change allows the removal of a service to be simulated by the Bluetooth test interface. To test the new function the script for generating service is removed tests is also updated to make use of the new function. BUG=569709 Change-Id: Ibb1c1dcfe3e7928c6628402d4a434847faf69e4e Reviewed-on: https://chromium-review.googlesource.com/825946 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Cr-Commit-Position: refs/heads/master@{#530582} 23 January 2018, 04:42:36 UTC
eb574c6 Charles Vazac 19 January 2018, 22:04:21 UTC Fix ServerTiming results for resources that fail TAO check Per spec (https://w3c.github.io/server-timing/#processing-model), resources that fail the TAO check should return an empty array for the serverTiming attribute. Bug: 802321 Change-Id: I0bca0f38f0a975f7c85f4d8837a901bd8475d9b7 Reviewed-on: https://chromium-review.googlesource.com/870990 Commit-Queue: Yoav Weiss <yoav@yoav.ws> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Cr-Commit-Position: refs/heads/master@{#530622} 23 January 2018, 04:32:10 UTC
8f6cb93 Ian Clelland 19 January 2018, 16:25:10 UTC Catch unexpected exceptions in sync-xhr test. With this change, only the expected NetworkError from send() will be propagated to the feature policy test framework. Other errors (including NetworkErrors from other calls) will be prefixed with "UnexpectedException:" and will cause the tests to fail. Bug: 661283 Change-Id: I75e2fa6526211cc87c65f5f03e926903ae1ba22e Reviewed-on: https://chromium-review.googlesource.com/874270 Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#530527} 23 January 2018, 04:23:58 UTC
a19b359 Darren Shen 20 January 2018, 06:55:38 UTC [css-typed-om] Update paint style map behaviour for invalid properties. Custom paint callbacks receive a computed style map (implemented as FilteredComputedStylePropertyMap) that contain only properties specified in inputProperties(). For forwards-compatiblity, inputProperties() is allowed to have "invalid" or shorthand properties, which are not allowed to be in the styleMap. As resolved in [1], the style map should ignore any invalid/shorthand properties. Furthermore, if a custom property is specified in inputProperties(), it should have a default value of CSSUnparsedValue() (not "null"). These changes also require changes in custom paint tests. Namely: - Can no longer get "border-radius" from the style map. Have to use a longhand property like "border-left-radius". - Getting custom properties like "--bar" will have a default value of CSSUnparsedValue. [1] https://github.com/w3c/css-houdini-drafts/issues/523 Bug: 803690 Change-Id: I148b52568de698f69ee0bf594a2b92a9751ea484 Reviewed-on: https://chromium-review.googlesource.com/874984 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Xida Chen <xidachen@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#530763} 23 January 2018, 04:13:44 UTC
2ea087e Rakina Zata Amni 23 January 2018, 03:40:31 UTC Fix retargeting of result in elementFromPoint and elementsFromPoint Currently elementFromPoint and elementsFromPoint are not per spec, and it may return null incorrectly. This change adds retargeting of the result with respect to the context object, and adds some tests that are similar to elementFromPoint tests in WebKit, but with some corrected cases: https://git.webkit.org/?p=WebKit-https.git;a=blob;f=LayoutTests/fast/shadow-dom/DocumentOrShadowRoot-prototype-elementFromPoint.html;h=a8dc4da2430713521b9ba77c742db10397a8e638;hb=HEAD Spec: https://w3c.github.io/webcomponents/spec/shadow/#extensions-to-the-documentorshadowroot-mixin Bug: 759947 Change-Id: I6aece5e9cc826124772c6ce13c806865055b2b9b Reviewed-on: https://chromium-review.googlesource.com/808446 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Cr-Commit-Position: refs/heads/master@{#531139} 23 January 2018, 03:51:32 UTC
a24f9d2 Darren Shen 23 January 2018, 02:29:15 UTC [css-typed-om] Clean up StylePropertyMap.get tests. This patch does the following to clean up the StylePropertyMap.get tests for WPT: - We split happy cases and sad cases into separate files. - We removed the .tentative extension. - Added additional tests for style map liveness. Bug: 774887 Change-Id: I4143b6358f0d2b11fbb34be03696d5eea00bd0fa Reviewed-on: https://chromium-review.googlesource.com/878104 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#531129} 23 January 2018, 03:29:30 UTC
2fc60fe Chris Cunningham 23 January 2018, 01:41:22 UTC De-dup two mediasource layout tests. Affected tests: http/tests/media/media-source/mediasource-addsourcebuffer.html http/tests/media/media-source/mediasource-is-type-supported.html The above were deleted after reconciling with their upstream WPT versions. Reconciling generally just adds new test conditions without removing any from the upstream version. The exception being the QuoteExceeded source buffer tests, where I've replicated the replacement of the original test with 2 new tests from the blink version. Change-Id: I2d3d483cf38e77eed3f26b5aab7fea0991a66723 Reviewed-on: https://chromium-review.googlesource.com/875161 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#531106} 23 January 2018, 02:29:11 UTC
3757743 Ovidio Henriquez 23 January 2018, 00:50:58 UTC bluetooth: Migrate canonicalize filter tests This change migrates the requestDevice/canonicalizeFilter tests to wpt/. BUG=509038 Change-Id: Idc05c345d12d83f0df1e88774defee70ac5a2eaf Reviewed-on: https://chromium-review.googlesource.com/837729 Reviewed-by: Conley Owens <cco3@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#531085} 23 January 2018, 02:05:53 UTC
a4f05cb Javier Fernandez 23 January 2018, 00:38:36 UTC [css-align] The 'left' and 'right' values must be invalid in block axis The CSS WG resolved to remove the 'left' and 'right' values from the block/cross axis alignment properties. https://github.com/w3c/csswg-drafts/issues/1403 This CL changes the CSS parsing logic of all the CSS Box Alignment properties, both block-axis (align-{self, items, content} and inline-axis (justify-{self, items, content}). Additionally, the alignment shorthands (place-{self, items, content}) have been also changed to respect the new syntax. This change also affects the Grid Layout alignment logic. Bug: 802095 Change-Id: Id848ce22a9b2d69ecf2bfd58503f590e4b2fe4db Reviewed-on: https://chromium-review.googlesource.com/877519 Reviewed-by: meade_(do not use) <meade@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#531074} 23 January 2018, 01:53:58 UTC
ca5f14e Mikhail Pozdnyakov 22 January 2018, 21:30:23 UTC [Sensors]Provide error codes from SensorProvider Return error codes from the SensorProvider.GetSensor() method. In future it will be used to return correct errors in Generic Sensor API (e.g. 'NotAllowedError' if permissions are denied). Bug: 796894 Change-Id: I613c6f3792fde3c05142f1b4cf809655b4acb15f Reviewed-on: https://chromium-review.googlesource.com/864325 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Alexander Shalamov <alexander.shalamov@intel.com> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com> Cr-Commit-Position: refs/heads/master@{#530997} 22 January 2018, 21:49:36 UTC
289fa0d Chris Lilley 22 January 2018, 18:22:02 UTC original test from https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=5188 22 January 2018, 18:22:02 UTC
ce7b5aa Chris Lilley 22 January 2018, 18:14:45 UTC original test from https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=5188 22 January 2018, 18:14:45 UTC
8d6c628 Philip Jägenstedt 22 January 2018, 15:05:21 UTC Move test for navigator.deviceMemory to its own dir with OWNERS Directory name matching https://w3c.github.io/device-memory/. Change-Id: If32f07b659aca91a63fd17ca80de4afb1cd525c2 Reviewed-on: https://chromium-review.googlesource.com/876423 Reviewed-by: Fadi Meawad <fmeawad@chromium.org> Reviewed-by: Shubhie Panicker <panicker@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#530859} 22 January 2018, 15:24:12 UTC
a9c9f5f Carlos Garcia Campos 22 January 2018, 13:49:02 UTC webdriver: response.py::test_pageLoadStrategy is using wrong capabilities Browser options should be included in alwaysMatch. 22 January 2018, 14:00:50 UTC
back to top