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
901c2f9 Raymond Toy 18 June 2018, 19:33:33 UTC Fix flaky k-rate-panner test Change the testing scheme for k-rate panner to verify that the output is piecewise constant for a constant source when the automation rate is set to k-rate. Reduce the duration of the test as well; Just a few render quanta is enough to verify that the output is piece-wise constant and different from the a-rate output. Also updated k-rate-constant-source.html to use the same doTest method since the special case is supported. Didn't actually figure out the underlying flakiness of the original test. Bug: 841856 Change-Id: I8e9807e530fc3b1452bae521a2660be3fbe104f9 Reviewed-on: https://chromium-review.googlesource.com/1076809 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#568100} 18 June 2018, 19:52:46 UTC
ba32f24 Simon Pieters 18 June 2018, 19:09:30 UTC Change permissions/OWNERS to permissions/META.yml 18 June 2018, 19:34:45 UTC
389b735 Simon Pieters 18 June 2018, 14:31:30 UTC [cssom-view] Remove redundant IDL tests Part of #11510. 18 June 2018, 17:44:15 UTC
ac16ec6 Simon Pieters 18 June 2018, 17:43:25 UTC [input-device-capabilities] Change from OWNERS to META.yml 18 June 2018, 17:43:25 UTC
00bb377 Simon Pieters 18 June 2018, 17:30:59 UTC Call done() in websockets/opening-handshake/003-sets-origin.worker.js (#11527) This prevents the test harness to time out. 18 June 2018, 17:30:59 UTC
e06f121 Geoffrey Sneddon 18 June 2018, 16:54:44 UTC Merge pull request #11496 (Update webidl2 to v13.0.3) 18 June 2018, 16:54:44 UTC
92bb4ac Rune Lillesveen 18 June 2018, 15:09:40 UTC Do not override kReattach for ::first-letter. We incorrectly did an override with kForce for ::first-letter recalc when we were already recalculating style for re-attachment (kReattach). This caused crashes in FirstLetterPseudoElement::DidRecalcStyle. Bug: 853621, 853476, 853471, 853470, 853433, 853411 Change-Id: Id34e6bdbaaeb3b4933a3e963b68f0bffcda0e40e Reviewed-on: https://chromium-review.googlesource.com/1104176 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#568006} 18 June 2018, 16:33:13 UTC
a6c9e70 Douglas Creager 18 June 2018, 14:05:42 UTC Reporting: Switch to underscores in headers and payloads This updates the Reporting implementation to include the naming changes in https://github.com/WICG/reporting/issues/72. Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I2446a8baaf512760949ac5bcaae56088def7d600 Reviewed-on: https://chromium-review.googlesource.com/1073060 Commit-Queue: Douglas Creager <dcreager@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Reviewed-by: Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#567990} 18 June 2018, 16:04:34 UTC
38dd912 jimevans 18 June 2018, 14:50:32 UTC Updating browser version retrieval for Chrome to return None on Windows (#11537) The test framework attempts to retrieve the version of Chrome by executing `chrome --version` and parsing the result. On Windows, this command simply launches the browser. There may be tehcniques that can be used on Windows to get this information, including, but not limited to, reading the value from the Windows registry. This commit simply returns None for the browser version, which is a valid return value for this method, and will not adversely affect the execution of the test framework. 18 June 2018, 14:50:32 UTC
7f0a106 Anne van Kesteren 08 June 2018, 10:48:10 UTC Fetch: test Cross-Origin-Resource-Policy: same-site's scheme restriction Supplements #11171. For https://github.com/whatwg/fetch/pull/733. 18 June 2018, 13:13:30 UTC
b7373b4 Anne van Kesteren 18 June 2018, 12:58:18 UTC Fetch: basic syntax tests for Cross-Origin-Resource-Policy Supplements #11171. For https://github.com/whatwg/fetch/pull/733. 18 June 2018, 12:58:18 UTC
7c0611d Philip Jägenstedt 18 June 2018, 12:54:14 UTC Move and simplify element.matches("*") test so that it works (#11229) The reason it didn't work before was because in Element-matches.js, it's always `someElement.matches("*")` being tested, which is the only thing that could be tested as there's not other "context" or "reference node" involved in the API surface. All of TEST_FIND is actually dead code, so dropping that is harmless. Fixes https://github.com/web-platform-tests/wpt/issues/11212. 18 June 2018, 12:54:14 UTC
53f7340 Youenn Fablet 25 May 2018, 20:29:16 UTC Fetch: Cross-Origin-Resource-Policy tests For https://github.com/whatwg/fetch/pull/733. WebKit export of https://bugs.webkit.org/show_bug.cgi?id=185840. 18 June 2018, 12:31:18 UTC
04a0711 moz-wptsync-bot 18 June 2018, 08:20:48 UTC [Gecko Bug 1323620] Add "fennec" product to wptrunner. (#11530) This allows running web-platform-tests on Fennec given a running emulator. (Which is how we expect the tests to run in automation as well -- the android_emulator_unittest mozharness script takes care of emulator start-up.) It also hooks up ./mach wpt. wptrunner sets up a profile for Fennec, forwards the marionette port and starts up Fennec, etc. = Usage = Set your mozconfig to build fennec. Start an emulator: `./mach android-emulator --version x86` Install fennec: `./mach build && ./mach package && ./mach install` Run the tests: ``` ./mach wpt --product=fennec --testtype=testharness --certutil-binary path/to/host/os/certutil path/to/some/tests ``` Differential Revision: https://phabricator.services.mozilla.com/D1587 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1323620 gecko-commit: 266c6cfb96a76daaa7bd2e3574f7d1d8ae60c4a6 gecko-integration-branch: autoland gecko-reviewers: jgraham 18 June 2018, 08:20:48 UTC
561fbb9 Hiroki Nakagawa 18 June 2018, 06:34:27 UTC ES Modules: Set referrer for top-level module script in ModuleScriptLoader Before this CL, referrer for top-level module script is set in BaseFetchContext::AddAdditionalRequestHeaders() using ExecutionContext::GetOutgoingReferrer(). This works for documents, but doesn't for workers because this execution context is corresponding to "module map settings object", not "fetch client settings object". To fix this, this CL sets the referrer for top-level module script using "fetch client settings object" in ModuleScriptLoader as the spec defines. Change-Id: I0878b13febdae4ee2dc56c998e7f2c100e9c1ba7 Bug: 842553 Reviewed-on: https://chromium-review.googlesource.com/1102236 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#567937} 18 June 2018, 06:42:10 UTC
38ef0a3 Dominic Farolino 18 June 2018, 06:01:48 UTC Consolidate console label conversion tests + add timeLog 18 June 2018, 06:01:48 UTC
6b14ce2 Dominic Farolino 18 June 2018, 05:54:06 UTC Inline factored out strings 18 June 2018, 05:54:06 UTC
d42d45d François Beaufort 18 June 2018, 05:43:27 UTC [Picture-in-Picture] Resolve with current window if video is pipElement. This make sures requestPictureInPicture is resolved with existing Picture-in-Picture window when video is already pictureInPictureElement. Bug: 806249 Change-Id: I16e3fc2e8e19c2b623e8d2518fe4672a2a16b756 Reviewed-on: https://chromium-review.googlesource.com/1101686 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#567934} 18 June 2018, 05:51:12 UTC
f055233 Abhishek Arya 17 June 2018, 18:37:12 UTC Revert "Floats and out-of-flow objects may not be adjacent to anonymous blocks." This reverts commit 2394d0acf8bf0b0236b2646e4c823a57de7bd941. Reason for revert: Caused ClusterFuzz regressions - 853522, 853537, 853538, 853540. Original change's description: > Floats and out-of-flow objects may not be adjacent to anonymous blocks. > > Floats and out-of-flow objects need to be true layout siblings of the > inlines, or rendering will be wrong. This means that such objects should > never be siblings of anonymous blocks, but rather inside them. This > already works correctly for initial layout tree building, and also for > many DOM manipulations. However, code was missing to satisfy this > requirement if we removed a regular block that was a sibling of an > anonymous block and either a float or out-of-flow positioned object. > > This even caused a crash triggered by ruby code, which ended up mixing > inline and block children within the same container. That is not > allowed. This happened in the MoveAllChildrenIncludingFloatsTo() call > inside LayoutRubyBase::MoveBlockChildren(). Added a DCHECK to > MoveAllChildrenIncludingFloatsTo() (which could fail prior to this fix); > When moving children from one container to another, either both or none > of the containers must have inline children. > > Bug: 852640 > Change-Id: I51d3de12c73ddd07d6b4c1aa55221b4f92359ca7 > Reviewed-on: https://chromium-review.googlesource.com/1102690 > Reviewed-by: Emil A Eklund <eae@chromium.org> > Commit-Queue: Morten Stenshorne <mstensho@chromium.org> > Cr-Commit-Position: refs/heads/master@{#567882} TBR=eae@chromium.org,mstensho@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 852640 Change-Id: I0af60d9eac770f21b6a0fbeccf88bb43d5efd6fb Reviewed-on: https://chromium-review.googlesource.com/1103503 Reviewed-by: Abhishek Arya <inferno@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#567914} 17 June 2018, 18:44:54 UTC
ab2182a Morten Stenshorne 16 June 2018, 15:56:18 UTC Floats and out-of-flow objects may not be adjacent to anonymous blocks. Floats and out-of-flow objects need to be true layout siblings of the inlines, or rendering will be wrong. This means that such objects should never be siblings of anonymous blocks, but rather inside them. This already works correctly for initial layout tree building, and also for many DOM manipulations. However, code was missing to satisfy this requirement if we removed a regular block that was a sibling of an anonymous block and either a float or out-of-flow positioned object. This even caused a crash triggered by ruby code, which ended up mixing inline and block children within the same container. That is not allowed. This happened in the MoveAllChildrenIncludingFloatsTo() call inside LayoutRubyBase::MoveBlockChildren(). Added a DCHECK to MoveAllChildrenIncludingFloatsTo() (which could fail prior to this fix); When moving children from one container to another, either both or none of the containers must have inline children. Bug: 852640 Change-Id: I51d3de12c73ddd07d6b4c1aa55221b4f92359ca7 Reviewed-on: https://chromium-review.googlesource.com/1102690 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#567882} 16 June 2018, 16:05:06 UTC
60cb800 Simon Pieters 16 June 2018, 10:24:02 UTC Change to META.yml 16 June 2018, 10:24:12 UTC
155a927 Simon Pieters 29 May 2018, 11:16:16 UTC Remove alvestrand, add henbos 16 June 2018, 10:24:12 UTC
a6da0ee Simon Pieters 24 April 2018, 19:46:25 UTC [webrtc-stats] add OWNERS 16 June 2018, 10:24:12 UTC
fdcd7c0 Brad Werth 15 June 2018, 23:45:22 UTC Part 5: Update a wpt reftest to remove its reliance on fitting inline-blocks into a too-narrow space. This reftest currently uses a container that is 1 pixel narrower than needed to fit two blocks side-by-side. That's useful for making the first two blocks land on separate lines, but it makes the test rely on the browser forcing the first inline block on a line to fit even if there is no space for it (in this case, the block that should be pushed to the right). bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466231 gecko-commit: 074014588d2f7d7afb821f68c3bd903f40d3152b gecko-integration-branch: autoland gecko-reviewers: dbaron 16 June 2018, 09:55:44 UTC
92a7dc8 Brad Werth 15 June 2018, 23:45:19 UTC Part 4: Correct the size of an element in a submitted WPT test, that was only passing due to this bug. This reftest was submitted by me with an incorrect size for the shape element. It was only passing in Firefox due to a related bug, which is now fixed. The updated size makes this test construct a polygon similar to the one in the shape-outside-polygon-012 test, which was the original intent. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466231 gecko-commit: 4d4ce1a9b81a955e84b16d6b54ffdd6b2f1c869b gecko-integration-branch: autoland gecko-reviewers: dbaron 16 June 2018, 09:55:44 UTC
de3ae39 Ehsan Karamad 15 June 2018, 20:19:40 UTC Ignore preventDefault on wheel (vertical-scroll) This CL implements the logic required for enforcing 'vertical-scroll' (through feature policy) on frames where a preventing mouse wheel handler may block vertical scrolling. The CL essentially overwrites the value of dispatch type from mouse wheel handlers iff the suggested direction of scrolling is vertical. Bug: 611982 Change-Id: I15230f11f616d093b21984fe0b526d94dc62dada Reviewed-on: https://chromium-review.googlesource.com/1073729 Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#567773} 15 June 2018, 20:31:14 UTC
a8f810f Simon Pieters 15 June 2018, 19:26:20 UTC Add variants 15 June 2018, 19:26:20 UTC
102eb17 Simon Pieters 15 June 2018, 19:11:22 UTC Include subset-tests.js correctly in encoding tests Fixes #11531. 15 June 2018, 19:11:22 UTC
dc7c5d6 Andy Paicu 15 June 2018, 16:02:38 UTC Prevent sandboxed documents from reusing the default window Bug: 377995 Change-Id: Iff66c6d214dfd0cb7ea9c80f83afeedfff703541 Reviewed-on: https://chromium-review.googlesource.com/983558 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#567663} 15 June 2018, 16:12:08 UTC
f3bc9cf Adam Rice 15 June 2018, 13:24:37 UTC Add test for WebSocket HTTP Authentication (#11433) User-agents should support HTTP authentication for WebSockets. Add a test of basic authentication to verify this. 15 June 2018, 13:24:37 UTC
be1bbf2 David Burns 15 June 2018, 04:35:19 UTC Enable keep-alive connections in wdclient for wdspec tests. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1468398 gecko-commit: 928ea511d72b187070bc1ca02cc80d799c318634 gecko-integration-branch: autoland gecko-reviewers: whimboo 15 June 2018, 12:24:12 UTC
6c10b8e Emilio Cobos Álvarez 15 June 2018, 07:15:08 UTC Move slot UA rule to html.css. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1468127 gecko-commit: 0f848f76f6e75bd99e3d56f5fff046efb516d2a0 gecko-integration-branch: autoland gecko-reviewers: xidorn 15 June 2018, 11:00:11 UTC
bb39a2f Henrik Boström 15 June 2018, 09:46:59 UTC Fix/improve external/wpt/webrtc/RTCPeerConnection-addTrack.https.html. Updated all tests to use promise_tests(), async/await and added cleanup logic for pc.close() in tests that did not already have that. Replaced broken test: 'addTrack with existing sender with null track, same kind, and sendrecv direction should create new sender' With: 'addTrack with existing sender that has not been used to send should reuse the sender', 'addTrack with existing sender that has been used to send should create new sender' Per-spec[1], if a sender has not been used to send (currentDirection never having had the value 'sendrecv' or 'sendonly') it may be reused, so the original test was incorrect. The new tests make sure that in the original scenario the sender IS reused, and in the case where the sender has been used a new sender is created instead of reusing, even if the original sender is no longer sending. In Unified Plan[2], all tests PASS. [1] Step 7 of https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack [2] Work-in-Progress CL https://chromium-review.googlesource.com/c/chromium/src/+/1025771 Bug: 777617 Change-Id: I2b07bc03d84add30999e0e017bf008fbc9e9f89a Reviewed-on: https://chromium-review.googlesource.com/1100828 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#567592} 15 June 2018, 09:55:37 UTC
0d616ec Yuki Shiino 15 June 2018, 09:02:24 UTC v8binding: Changes @@unscopables's prototype to ES null. Implements step 8.1. of https://heycam.github.io/webidl/#create-an-interface-prototype-object Bug: 811029 Change-Id: I0feb1c16cf12585db8847c82d4efa342701bebcb Reviewed-on: https://chromium-review.googlesource.com/1098914 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#567580} 15 June 2018, 09:11:55 UTC
83fd220 Mike West 15 June 2018, 07:28:12 UTC `Sec-Metadata`: `cause` is navigation-only. This patch removes the `cause` member from `Sec-Metadata` headers generated for non-navigation requests. Spec: https://mikewest.github.io/sec-metadata/#cause-member Bug: 843478 Change-Id: I1cc35909ecdccd7ac0f4ab440be899acf67a0181 Reviewed-on: https://chromium-review.googlesource.com/1100820 Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#567571} 15 June 2018, 07:38:28 UTC
c1f6ae4 Kagami Sascha Rosylight 15 June 2018, 06:46:26 UTC fix configparser error 15 June 2018, 06:46:26 UTC
8908785 Mike Pennisi 14 June 2018, 16:49:56 UTC [testdriver.js] Correct typos 15 June 2018, 04:58:20 UTC
58a9a81 Kagami Sascha Rosylight 15 June 2018, 04:09:08 UTC fix py3 syntax/import errors on pywebsocket 15 June 2018, 04:09:08 UTC
491761a Kagami Sascha Rosylight 15 June 2018, 02:45:48 UTC escape audio idls 15 June 2018, 02:45:48 UTC
a807ff2 Kagami Sascha Rosylight 15 June 2018, 02:42:41 UTC move pointerevents-ext idl into interfaces 15 June 2018, 02:42:41 UTC
002fba8 Morten Stenshorne 14 June 2018, 21:48:09 UTC [LayoutNG] Don't update a block's intrinsic block size prematurely. Assuming that every child block end offset contribute to intrinsic block size of the container is wrong. There may be negative margins. Calculate it after child layout, rather than during child layout for each in-flow child. Some extra care was required for NG block fragmentation, because there was code that updated (and checked) the intrinsic size rather than logical block offset. Using intrinsic size will no longer get us anywhere, since it's now only updated at the end of container layout, not during child layout. Move the initialization of intrinsic block size (set to content edge) after layout instead of before layout, to reduce variable span. We may eventually want to change it to a local variable instead of a member. Fixes 9 tests, 7 of which were not marked as failing, but rather had incorrect NG-specific baselines. Also wrote 2 new tests that test this fix a bit more directly. Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: Id57ba18b70f0cc8569deeff63fa5547cb8c44c98 Reviewed-on: https://chromium-review.googlesource.com/1100473 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#567429} 14 June 2018, 21:58:00 UTC
1249dcc Chris Nardi 14 June 2018, 21:34:59 UTC Use Referrer Policy IDL as dependency for fetch (#11515) In newer versions of webidl2.js, empty enums are not allowed. We can easily switch to using the actual definition in the Referrer Policy spec to avoid running into any problems when upgrading webidl2.js. This change leads to the same number of passing/failing tests on Chrome. 14 June 2018, 21:34:59 UTC
5b644a9 Simon Pieters 13 June 2018, 19:11:18 UTC Update references to OWNERS Fixes #11487. 14 June 2018, 21:20:32 UTC
582057a Luke Bjerring 14 June 2018, 20:56:34 UTC Update the webappsec-referrer-policy IDL file (#9847) Add webappsec-referrer-policy IDL file 14 June 2018, 20:56:34 UTC
89c5dcd Hiroshige Hayashizaki 14 June 2018, 18:27:32 UTC Evaluate child text content at the time of #prepare-a-script, not evaluation Previously, classic inline script's source_text to be evaluated is taken from the element's child text content at the time of evaluation. However, according to the spec, this should be the element's child text content at the time of #prepare-a-script. This CL fixes this by taking the element's child text content in ClassicPendingScript's constructor, which is called inside PrepareScript(). This affects the behavior if parser-inserted classic inline <script>'s innerText is modified by JavaScript after <script> is inserted into DOM before its evaluation, and I expect this is extremely rare and doesn't have legitimate use cases. Bug: 686281 Change-Id: I0ef67dd8b71403a7862f24d02394f89c6e916bfd Reviewed-on: https://chromium-review.googlesource.com/1091912 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#567348} 14 June 2018, 18:42:22 UTC
af99298 codeimpl 14 June 2018, 18:07:38 UTC Rename XRFrameOfReferenceType enums The values of the enum was updated in the spec[1]. [1] https://github.com/immersive-web/webxr/pull/370 Bug: 852520 Change-Id: I916943bee355936e7430aa4e36d0eeb6b76607d5 Reviewed-on: https://chromium-review.googlesource.com/1101118 Reviewed-by: Brandon Jones <bajones@chromium.org> Commit-Queue: Byoungkwon Ko <codeimpl@gmail.com> Cr-Commit-Position: refs/heads/master@{#567340} 14 June 2018, 18:27:27 UTC
0ccf8bb Raphael Kubo da Costa 14 June 2018, 17:08:44 UTC CSSStyleDeclaration: Stop calling ScriptState::ContextIsValid() in the setter When the custom bindings were removed in commit 5b84e88a0 ("Remove custom bindings for CSSStyleDeclaration"), the new anonymous setter code added a check for ScriptState::ContextIsValid() to ensure it had received a valid |script_state|. It turns out this check is too strict, as in addition to verifying a ScriptState has an associated v8::Context it also asserts the ScriptState has a valid |per_context_data_|. This is valid in most cases, but when a node is moved across different documents and its previous document gets removed its |per_context_data_| is disposed of and ScriptState::ContextIsValid() fails. Since the anonymous setter is only invoked by the bindings layer, we can assume it is passed a ScriptState that is in a minimally usable state, so it is possible to relax the ContextIsValid() check and only make sure we can get a valid ExecutionContext from the ScriptState. Bug: 852190 Change-Id: I307de0e003e5258bf1f670b26f1dc86e4dae9286 Reviewed-on: https://chromium-review.googlesource.com/1100836 Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#567310} 14 June 2018, 18:27:23 UTC
134fd45 Marijn Kruisselbrink 14 June 2018, 17:08:36 UTC Add a web platform test to verify various aspects of creating workers from blobs. Bug: 852249, 800898 Change-Id: Ic885db66683d40f259f4f8c0ddf82d6ea3b4c144 Reviewed-on: https://chromium-review.googlesource.com/1099361 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#567308} 14 June 2018, 18:17:39 UTC
d959a1e Manuel Rego Casasnovas 14 June 2018, 16:18:47 UTC [css-contain] Disable size containment for tables The CSSWG resolved about it in the last meeting: https://github.com/w3c/csswg-drafts/issues/2746 BUG=843329 TEST=external/wpt/css/css-contain/contain-size-012.html Change-Id: Ibb037f9ab1b95bed03e46fdbeb0e68520ff741b4 Reviewed-on: https://chromium-review.googlesource.com/1100824 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#567289} 14 June 2018, 17:18:25 UTC
7cbefa7 Wanming Lin 14 June 2018, 16:33:10 UTC Fix partial issues from #10198 (#10962) - `if (testRunner)` should be `if (window.testRunner)` - Use String to pass sensor object param to avoid undefined error 14 June 2018, 16:33:10 UTC
55c9a77 Luke Bjerring 14 June 2018, 16:07:34 UTC Update the server-timing IDL file (#9831) 14 June 2018, 16:07:34 UTC
41a040a Alice Boxhall 14 June 2018, 15:11:59 UTC Improve :focus-visible tests - Add explanatory text to each one - Make the manual test path accessible to color blind testers - Bring headers up to date - Create a consistent style for :focus-visible and :focus:not(:focus-visible) for easier understanding of test results Bug: 817199 Change-Id: I97191d5c8395576a42c923a025d05d2d61e79552 Reviewed-on: https://chromium-review.googlesource.com/1093697 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Cr-Commit-Position: refs/heads/master@{#567266} 14 June 2018, 15:31:12 UTC
a639bff L. David Baron 14 June 2018, 14:50:30 UTC Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/91db0c695f0272f00bf92c81c471a85101056d96 . (#11505) 14 June 2018, 14:50:30 UTC
0872560 Luke Bjerring 14 June 2018, 12:51:24 UTC Clean up the webaudio idl test and add long timeout Bug: 851320 Change-Id: I562fe492be73b0ad8929d8ae8be158230103157f Reviewed-on: https://chromium-review.googlesource.com/1095640 Reviewed-by: Raymond Toy <rtoy@chromium.org> Commit-Queue: Luke Bj <lukebjerring@chromium.org> Cr-Commit-Position: refs/heads/master@{#567231} 14 June 2018, 13:01:02 UTC
55d4477 Raphael Kubo da Costa 14 June 2018, 12:44:07 UTC docs: Add missing "be" to testharness' documentation 14 June 2018, 12:53:45 UTC
73f8f23 Simon Pieters 14 June 2018, 12:43:34 UTC Fail early if Feature Policy is not supported (#11270) Part of #11269. 14 June 2018, 12:43:34 UTC
cf68763 Marcos Cáceres 14 June 2018, 12:16:32 UTC PaymentRequest "paymentmethodchanged" event (#10912) 14 June 2018, 12:16:32 UTC
1b58a73 Philip Jägenstedt 14 June 2018, 10:20:34 UTC Strip webrtc/ prefix 14 June 2018, 10:20:34 UTC
157e35f Kagami Sascha Rosylight 14 June 2018, 07:29:10 UTC fix error type test 14 June 2018, 07:29:10 UTC
f556cda Morten Stenshorne 14 June 2018, 06:30:16 UTC [LayoutNG] Avoid creating empty lines at bogus (unset) BFC offset 0,0. This affects auto-positioned out-of-flow nodes that are handled as part of inline layout, and other things too. This fix will also make it possible to use the position of the last child fragment to calculate the block size of a block (which I happen to be working on). Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ie3f99d850de81bd349e89c624f86cce95b38eede Reviewed-on: https://chromium-review.googlesource.com/1098925 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#567170} 14 June 2018, 06:39:23 UTC
2b5b598 Kagami Sascha Rosylight 14 June 2018, 06:11:43 UTC fix return value test 14 June 2018, 06:11:43 UTC
ff95351 Kagami Sascha Rosylight 14 June 2018, 05:08:33 UTC Merge commit 'a94782e9431b2839d4ae40ab5a62ad553dcbd6ed' into webidl2-13 14 June 2018, 05:08:33 UTC
a94782e Kagami Sascha Rosylight 14 June 2018, 05:08:16 UTC Squashed 'resources/webidl2/' changes from dd57b9f0db..83cd4a064a 83cd4a064a chore(package): bump version number to 13.0.3 c4492f2f71 refactor(lib/writer): remove args() (#184) b3b100f746 refactor: consume argument name in object spread way (#183) 4aff72ec29 chore(package): bump version number to 13.0.2 d5f335a033 fix: allow required for an attribute name (#182) 835e835461 chore(package): bump version number to 13.0.1 a209033036 refactor: unconsume by position (#179) 494d31da45 chore(package-lock): run npm audit fix e2e83ac629 chore(package): bump version number to 13.0.0 8d04da9ed0 fix: consume return type for promise subtype (#177) f116f14b97 add probe() function (#176) eed64a06a3 BREAKING CHANGE: remove idlType.sequence (#175) e6a76a1575 fix: prevent incorrect spaced negative infinity and variadic marks (#173) 809e640d78 refactor: merge operation functions (#172) cb558a3eff fix: allow selected keywords in argument name (#171) bbb47c2174 fix: write inherit readonly attribute in proper order (#170) 2babd47e1f refactor: merge attribute functions (#166) 2ccd34fe18 chore(package): bump version number to 12.1.4 7cd23cdad5 fix: prevent readwrite attributes on namespaces (#165) ddbc4a5682 chore(package): bump version number to 12.1.3 8628744060 fix: prevent incorrect union types (#163) 60859b5253 chore(package): bump version number to 12.1.2 a73d090a31 fix(package.json): add file extension in the main field 2827821f2f chore(package): bump version number to 12.1.1 d639527ed1 fix: prevent tokeniser error when it meets _0 (#161) 568675358b add files field to package.json (#160) 68a37d21e8 chore(package): bump version number to 12.1.0 621d0b6c17 fix: prevent keywords from being identifiers (#157) 9ad8932034 chore(package): bump version number to 12.0.0 a154b63cea BREAKING CHANGE: remove allowNestedTypedefs (#155) 5a495f76a5 refactor: remove all_ws() and gather trivia implicitly (#154) e717aa67fa tests: Remove test/widlproc (#153) 131e74cc57 chore(package): bump version number to 11.0.0 09f8a1daae Prevent incorrect enums (#151) fa060611a9 BREAKING CHANGE: remove opt.ws (#150) 2bb4e1cbb2 chore(package): bump version number to 10.3.3 (#149) 80936fa3c9 oefactor simple_extended_attr() (#148) c060079cca docs: remove description about typePair (#147) 4169268630 docs: simple WebIDL checker. (#146) a28c7b55f7 chore(package): bump version number to 10.3.2 e311680dc0 fix: correctly handle whitespaces of implements and includes. (#145) 50c828344d refactor: remove eas.length check (#144) 968ca63fd4 refactor: one-to-one match for token matcher (#143) 8531535861 chore(package): bump version number to 10.3.1 96deeb3480 const-type as full IDL Type (#142) a13dfa8cf5 chore(package): bump version number to 10.3.0 c0ab164af2 always add extAttrs for .idlType (#141) 932dcfb96d docs(README): add missing typedef-type 56777f49dc docs(README): add missing types-of-types c14d7c1767 docs(README): add types of types (#140) 730a3b99db chore(CHANGELOG): regenerate git-subtree-dir: resources/webidl2 git-subtree-split: 83cd4a064a3a183268c4d6af0556a3f981f509c1 14 June 2018, 05:08:16 UTC
b12b605 Mike Pennisi 13 June 2018, 23:51:41 UTC [docs] Add instruction for specifying test title 14 June 2018, 04:40:49 UTC
1110f36 Luke Bjerring 14 June 2018, 03:47:18 UTC Update webusb test Upstream re-attempt at https://github.com/web-platform-tests/wpt/pull/9854. Adds more untested IDL deps. Change-Id: Icf7bda0f264ec66f4980e0742485eb406e334c19 Reviewed-on: https://chromium-review.googlesource.com/1089862 Commit-Queue: Luke Bj <lukebjerring@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#567118} 14 June 2018, 03:55:25 UTC
66f3830 Morten Stenshorne 13 June 2018, 23:07:13 UTC Avoid ~infinite table max logical width inside flex and grid containers. An infinite (or actually kTableMaxWidth, which is 1000000px) max logical width doesn't work well inside flexboxes, because LayoutFlexibleBox::ComputeInnerFlexBaseSizeForChild() will use a child's MaxPreferredLogicalWidth() as main axis extent if it's auto. Grid containers have similar issues with such tables, so avoid it for them as well. Don't apply this to deprecated flexbox, as that would cause two tests failures: * fast/block/block-size-integer-overflow.html * fast/deprecated-flexbox/box-size-integer-overflow.html Bug: 850566 Change-Id: I9984459801ac229575e8177a9d683088e723db6c Reviewed-on: https://chromium-review.googlesource.com/1095220 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#567032} 13 June 2018, 23:18:56 UTC
3172a6c Alex Chiem 13 June 2018, 23:01:26 UTC webdriver: add element_click tests (#11453) 13 June 2018, 23:01:26 UTC
c941a55 Geoffrey Sneddon 12 June 2018, 16:59:54 UTC Fix WptreportFormatter support for mozlog suites with no run_info Per the mozlog docs run_info is "an optional dictionary" 13 June 2018, 17:40:33 UTC
4fd6e87 Geoffrey Sneddon 12 June 2018, 16:55:45 UTC Fix #10026: add test execution time to wptreport.json format 13 June 2018, 17:40:33 UTC
fec5f26 C. Van Wiemeersch 13 June 2018, 17:05:41 UTC fix `python wpt make-hosts-file` command in README for PowerShell on Windows 10 (#11367) 13 June 2018, 17:05:41 UTC
5a2bb75 Simon Pieters 13 June 2018, 15:34:02 UTC Fix linter to not complain about META.yml (#11486) Fixes #11484. 13 June 2018, 15:34:02 UTC
a027205 Ehsan Karamad 13 June 2018, 14:50:41 UTC Rename Feature Policy: document-stream-insertion It was proposed here https://github.com/WICG/feature-policy/pull/172 that "document-write" is a better name for this feature. This CL makes the naming change correspondingly. Bug: 841605 Change-Id: Id0a928fd3f6669eb3700736ff5770d4717d2b414 Reviewed-on: https://chromium-review.googlesource.com/1095328 Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#566829} 13 June 2018, 15:02:00 UTC
5f202c8 Gerald Squelart 12 June 2018, 02:11:48 UTC Test ascii-case-insensitivity of media query expressions bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1464091 gecko-commit: 32a24b5f542d6f14f11c8c2cc32180066c4c8b62 gecko-integration-branch: autoland gecko-reviewers: heycam 13 June 2018, 09:26:11 UTC
9bf1daa Simon Pieters 13 June 2018, 09:13:34 UTC [idlharness.js] Support subsetTestByKey in idlharness (#11414) Fixes #11413. 13 June 2018, 09:13:34 UTC
4f741e6 Simon Pieters 12 June 2018, 22:42:42 UTC Order both actual and expected in selftests (#11425) 12 June 2018, 22:42:42 UTC
c78f060 Luke Bjerring 12 June 2018, 21:53:08 UTC Auto-update the xhr IDL source (#11465) 12 June 2018, 21:53:08 UTC
2b9df3e Luke Bjerring 12 June 2018, 21:51:53 UTC Add css-paint-api IDL file with test (#9773) 12 June 2018, 21:51:53 UTC
e600ea2 Jonathon Kereliuk 12 June 2018, 21:30:41 UTC Rename of OWNER files to META.yml 12 June 2018, 21:30:41 UTC
e4ef2f7 Chris Lilley 12 June 2018, 20:19:20 UTC Merge pull request #11480 from gsnedders/c563-list-type-000-ref-fix Fix c563-list-type-000-ref to match the test 12 June 2018, 20:19:20 UTC
be5b31e Geoffrey Sneddon 12 June 2018, 18:33:21 UTC Fix c563-list-type-000-ref to match the test 12 June 2018, 18:33:21 UTC
33280b7 Geoffrey Sneddon 12 June 2018, 18:13:57 UTC Fix #11454: Set --verify-log-full to False for ci/check_stability.py (#11464) I'm not entirely sure why #10988 made this default to on, given that was a change of behaviour from before, so let's turn it back off given it's causing breakage, as documented in #11454. 12 June 2018, 18:13:57 UTC
98530fb Marijn Kruisselbrink 12 June 2018, 16:54:47 UTC Fix test flakiness around multi-threaded blob URL revocation. Registering a new blob URL in the worker will ensure (at least in chrome) that the revocation has been fully processed before the main thread tries to fetch the now revoked URL. Bug: 851942 Change-Id: I12e794682dbb5b34dc08fe2a7d398e3ba02aaffa Reviewed-on: https://chromium-review.googlesource.com/1097230 Reviewed-by: Joshua Bell <jsbell@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#566460} 12 June 2018, 17:04:04 UTC
c81e348 Jim Evans 12 June 2018, 14:56:30 UTC Remove array destructuring for WebDriver execute async script tests IE does not support array destructuring in a `let` statement. This commit allows the execute_async_script tests for collections to run on IE 11. 12 June 2018, 16:16:11 UTC
692f3f4 Henrik Boström 12 June 2018, 15:51:34 UTC Fix errors in external/wpt/RTCDTMFSender-insertDTMF.https.html. This is in preparation for RTCRtpTransceiver/Unified Plan support. Updated tests: insertDTMF() should throw InvalidStateError if transceiver.currentDirection is [recvonly/inactive] Just like the tests fixed in https://chromium-review.googlesource.com/c/chromium/src/+/1095275, the tests were not set up properly. Fixed the tests so that currentDirection is what it is supposed to be according to the test description. Also updated the tests to use async/await. These tests will pass when we support RTCRtpTransceiver (WIP CL: https://chromium-review.googlesource.com/c/chromium/src/+/1025771). Bug: 777617 Change-Id: I59eab4e4a15bb82e2dabe68d56f6d55b0e380e75 Reviewed-on: https://chromium-review.googlesource.com/1097083 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#566432} 12 June 2018, 16:01:56 UTC
a65ac19 Geoffrey Sneddon 12 June 2018, 15:41:50 UTC Fix F401 (unused import) throughout tools/ (#11439) 12 June 2018, 15:41:50 UTC
73ed379 Javier Fernandez 12 June 2018, 14:29:03 UTC [css-grid] Content Alignment as part of the track sizing algorithm The CSS WG resolved [1] that Content Alignment should account to the track sizing algorithm. The sizing algorithm has been modified so that two new steps (1.5 and 2.5) were added to compute the Content Alignment offsets after resolving the columns' and rows' sizes respectively. This change decouples the Content Alignment logic from the tracks position, so that we can use it as part of the track sizing algorithm. I also had to store the whole ContentAlignmentData structure in two class attributes. We need both, position and distribution offsets, to be used in different parts of the layout logic. Finally, since the ContentAlignmentData is now used as persistent memory, we had to remove the STACK_ALLOCATED flag; hence, I think using DISALLOW_COPY_AND_ASSIGN and let the functions update the structure's internal field is a more efficient approach to commit this change. [1] https://github.com/w3c/csswg-drafts/issues/2557 Added WPT * grid-content-distribution-must-account-for-track-sizing-001.html * grid-content-distribution-must-account-for-track-sizing-002.html Bug: 844744 Change-Id: I90019a96b148d3713467e35fde9482d0d39b1ced Reviewed-on: https://chromium-review.googlesource.com/1067918 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#566412} 12 June 2018, 14:50:42 UTC
ce580da Luke Bjerring 12 June 2018, 13:33:43 UTC Clean up FileAPI idlharness tests After fixing #10338, we can leverage add_dependency_idls to import the 'real' untested idl from sources cleanly. 12 June 2018, 13:33:43 UTC
c08f464 Henrik Boström 12 June 2018, 11:21:39 UTC nit wpt/webrtc/: Fix missing argument in RTCPeerConnection-getStats. TBR=guidou@chromium.org NOTRY=True Bug: 777617 Change-Id: Ia6e81728d3dfac35c9b1724252e7539b3aae181a Reviewed-on: https://chromium-review.googlesource.com/1096944 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#566381} 12 June 2018, 11:30:01 UTC
05c1a1f Kent Tamura 12 June 2018, 10:26:24 UTC custom-elements: Element created by createElementNS(ns, qname, options) with valid custom element name and undefined options should be upgraded immediately createElementNS(XHTML_NS, 'my-element', undefined) was not being upgraded immediatedly, though both createElementNS(XHTML_NS, 'my-element') and createElementNS(XHTML_NS, 'my-element', {}) were. Bug: 841725 Change-Id: Iccc4f0e98b1de65288381dd9ac106e71bfc5d0c8 Reviewed-on: https://chromium-review.googlesource.com/1096812 Reviewed-by: Yoichi Osato <yoichio@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#566374} 12 June 2018, 10:36:03 UTC
ae0eec1 Henrik Boström 12 June 2018, 10:16:32 UTC Fix errors external/wpt/RTCPeerConnection-removeTrack.https.html. This is in preparation for RTCRtpTransceiver/Unified Plan support. "Calling removeTrack with valid sender should set sender.track to null" Asserting that direction changes from 'sendrecv' to 'recvonly', this is explicit in the spec[1]. "Calling removeTrack with currentDirection blah should set direction to blah" The tests that meant to set up currentDirection to be 'sendrecv' or 'recvonly' before removeTrack() were incorrect. Tests updated to set up currentDirection correctly. Also updated them to use async/await because that's much nicer. These all fail because we don't have transceivers yet, but when running these changes in the RTCRtpTransceiver WIP CL[2], they all pass. [1] See step 10 of https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-removetrack [2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771/ Bug: 777617 Change-Id: Ie3c077d14ea30038a06a98ecbeea475ac824dd9c Reviewed-on: https://chromium-review.googlesource.com/1095275 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#566366} 12 June 2018, 10:26:20 UTC
ed8650a Florian Rivoal 12 June 2018, 09:36:37 UTC Merge pull request #11335 from frivoal/git-doc-lint Mention the lint tool in the github tutorial 12 June 2018, 09:36:37 UTC
67ad035 Tarun Bansal 12 June 2018, 08:53:09 UTC Add web platform test for Accept-CH-Lifetime header for client hints Bug: 817049 Change-Id: Ic58e5688b0bb14803a9b6f01100500dd567b9fbc Reviewed-on: https://chromium-review.googlesource.com/1066919 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#566359} 12 June 2018, 09:01:35 UTC
2eeb9f0 Florian Rivoal 12 June 2018, 06:27:41 UTC Phrasing improvements and typo fixes 12 June 2018, 06:27:56 UTC
af6293e Manuel Rego Casasnovas 12 June 2018, 01:50:36 UTC [css-contain] Size containment should ignore contents in flexbox/grid The spec is pretty clear (https://drafts.csswg.org/css-contain/#containment-size): "1. When laying out the containing element, it must be treated as having no contents." The patch modifies ComputeIntrinsicLogicalWidths() and FirstLineBoxBaseline() in LayoutFlexibleBox and LayoutGrid, so the contents are ignored if the flex or grid container has "contain: size". Buttons are implemented as flexboxes internally, so they get fixed too thanks to this change. BUG=850169 TEST=external/wpt/css/css-contain/contain-size-button-001.html TEST=external/wpt/css/css-contain/contain-size-flexbox-001.html TEST=external/wpt/css/css-contain/contain-size-grid-001.html Change-Id: Ia08c2c7b31126911cb4f0d1fc70aa444c22af8e3 Reviewed-on: https://chromium-review.googlesource.com/1093854 Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#566228} 12 June 2018, 02:01:26 UTC
be95940 Raymond Toy 11 June 2018, 22:58:11 UTC Adjust test thresholds for win10 These tests fail on Windows 10 because the error thresholds are a bit too tight. Relax them a bit so that these pass on my Win10 machine. Bug: 851605 Change-Id: Ie7795205550a43928e7f0963e4411264e3ded37b Reviewed-on: https://chromium-review.googlesource.com/1095859 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#566181} 11 June 2018, 23:08:40 UTC
0899588 Mike Pennisi 24 May 2018, 17:04:15 UTC [testharness.js] Extend test suite with "variants" Feature description (from modification to `README.md` file): > `testharness.js` is expected to function consistently in a number of > distinct environments. In order to verify this expectation, each functional > test may be executed under a number of distinct conditions. These conditions > are applied using WPT's "test variants" pattern. The available variants are > defined in the `variants.js` file; this file must be included before > `testharness.js`. Every test must specify at least one variant. Extend test harness for `testharness.js` with additional validation to ensure that each test is correctly formatted. Introduce a minimal UI to help future contributors discover this new functionality and its motivation. 11 June 2018, 21:04:28 UTC
46fe680 Alexander Shalamov 11 June 2018, 19:19:13 UTC [sensors] Check that sensor frame and focused frame of same origin In order to implement mitigation stragegy defined in [1], focused frame and frame associated with the sensor should be of the same origin. [1] https://www.w3.org/TR/generic-sensor/#focused-area Bug: 849501 Change-Id: I06fce4e66873cd98e59e45d00ffe27de8e7d66f9 Reviewed-on: https://chromium-review.googlesource.com/1087049 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Alexander Shalamov <alexander.shalamov@intel.com> Cr-Commit-Position: refs/heads/master@{#566096} 11 June 2018, 19:59:32 UTC
8b2d92a Simon Pieters 05 June 2018, 08:03:22 UTC Offscreen canvas: make worker tests catch errors Part of #11269. 11 June 2018, 19:05:44 UTC
32f74fe nanto_vi, TOYAMA Nao 11 June 2018, 19:01:42 UTC "Scroll an element into view" in HTML spec I use assert_approx_equals here since properties of DOMRect are of type double. For https://github.com/whatwg/html/pull/3131. 11 June 2018, 19:01:42 UTC
2c4b6f9 Simon Pieters 11 June 2018, 16:15:46 UTC HTML: Run a history navigation test in a popup to report a result (#11296) Part of #11269. 11 June 2018, 16:15:46 UTC
back to top