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
df4bdf5 Florian Rivoal 29 March 2018, 06:13:03 UTC [css-overflow] Add the spec editors as OWNERS 29 March 2018, 06:13:03 UTC
55846d5 Zhuoyu Qian 29 March 2018, 01:09:38 UTC Check BackgroundEdgeOrigin when check BackgroundPosition. We should check Background{X/Y}Origin when check BackgroundPosition{X/Y}. BackgroundPosition same but BackgroundEdgeOrigin different is not the same position, we should return false when FillLayersEqual(). Bug: 823046 Signed-off-by: Zhuoyu Qian <zhuoyu.qian@samsung.com> Change-Id: Ia7d0c5af33e1ee5986420dc054c2ce1b1f65e9b0 Reviewed-on: https://chromium-review.googlesource.com/967912 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#546679} 29 March 2018, 01:19:15 UTC
592e2ed Brian Burg 29 March 2018, 00:42:03 UTC webdriver: add more WebKit workarounds to detect whether a window is fullscreen (#10226) WebKit doesn't implement the Fullscreen API yet, so we need to use the vendor prefixed property to check whether the window is fullscreen. This workaround was previously applied to fullscreen_window.py, but it needs to happen in other places as wel. 29 March 2018, 00:42:03 UTC
bc7c640 Luke Bjerring 28 March 2018, 22:30:58 UTC Support partial dictionaries (#10159) * Support partial dictionaries 28 March 2018, 22:30:58 UTC
d5fea75 François Doray 28 March 2018, 20:58:32 UTC Revert "bluetooth: FakeBluetoothChooser impl." This reverts commit 188adfb51a7c4ca1ab0cbeaffdec4f7cd76857f7. Reason for revert: https://crbug.com/826787 Original change's description: > bluetooth: FakeBluetoothChooser impl. > > Implements the interfaces that FakeBluetoothChooser overrides. The > mojom::FakeBluetoothChooser overrides are implemented by running > |event_handler_| with the appropriate arguments. The BluetoothChooser > overrides do nothing at the moment, since the base class is only meant > to update the chooser user interface. > > This change also begins to partially convert a Bluetooth chooser test to test > the interface and deletes the temporary tests that were created to test this > API. > > BUG=719827,719826,824704 > > Change-Id: I56a04e6bdb2de38d9163d7bc350db578deeb9ba3 > Reviewed-on: https://chromium-review.googlesource.com/962983 > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Conley Owens <cco3@chromium.org> > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> > Cr-Commit-Position: refs/heads/master@{#546509} TBR=dcheng@chromium.org,cco3@chromium.org,ortuno@chromium.org,odejesush@chromium.org Change-Id: I0597151ec5878d41ac631b72296203bc99b1f2c8 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 719827, 719826, 824704, 826787 Reviewed-on: https://chromium-review.googlesource.com/984299 Commit-Queue: François Doray <fdoray@chromium.org> Reviewed-by: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#546572} 28 March 2018, 21:20:02 UTC
c2cd757 Ian Kilpatrick 28 March 2018, 04:35:58 UTC [css-layout-api] Implementation of LayoutConstraints#fixedInlineSize. This adds the bare bones for the LayoutConstraints object. It just handles the fixedInlineSize parameter. I expect the information in this object after the next F2F. The layout for the test will simply output an autoBlockSize of 100, if the fixedInlineSize is 100. The tests impose various conditions in how this can occur, but is certainly not exhaustive. Change-Id: I6be4a7b77d7b737c778dc2de8b235035b8d3fa22 Bug: 726125 Reviewed-on: https://chromium-review.googlesource.com/981517 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#546393} 28 March 2018, 21:08:43 UTC
107dd46 Ovidio Henriquez 28 March 2018, 16:19:20 UTC bluetooth: FakeBluetoothChooser impl. Implements the interfaces that FakeBluetoothChooser overrides. The mojom::FakeBluetoothChooser overrides are implemented by running |event_handler_| with the appropriate arguments. The BluetoothChooser overrides do nothing at the moment, since the base class is only meant to update the chooser user interface. This change also begins to partially convert a Bluetooth chooser test to test the interface and deletes the temporary tests that were created to test this API. BUG=719827,719826,824704 Change-Id: I56a04e6bdb2de38d9163d7bc350db578deeb9ba3 Reviewed-on: https://chromium-review.googlesource.com/962983 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#546509} 28 March 2018, 20:53:27 UTC
7c782f4 Ben Kelly 28 March 2018, 19:46:15 UTC P2 Add a WPT test verifying synthetic responses work when a request fragment is present. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1443850 gecko-commit: 7b66eb1629750401eb5768646d8381ff4e631cac gecko-integration-branch: central gecko-reviewers: asuth 28 March 2018, 20:23:21 UTC
49b9015 Boris Zbarsky 28 March 2018, 19:09:05 UTC part 2. Add a bunch of web platform tests for load and error events on stylesheet links. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1443652 gecko-commit: 7daaf289c085e05e0e4a0327a13748002fb467a0 gecko-integration-branch: central gecko-reviewers: bholley 28 March 2018, 19:49:20 UTC
7b35f2c Boris Zbarsky 28 March 2018, 19:09:02 UTC part 1. Fix the buggy existing load-event test for stylesheets. The test was adding the load listener to the <link> _after_ the load event on the <link> had already fired. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1443652 gecko-commit: ba6cef216a171782bd8abcd00a08c9ae88cbfe43 gecko-integration-branch: central gecko-reviewers: bholley 28 March 2018, 19:49:20 UTC
355c2d7 Luke Bjerring 28 March 2018, 19:30:20 UTC Handle idlharness.js expected errors as an IdlArray.assert_throw option (#10164) * Handle idlharness.js expected errors as an IdlArray.assert_throw option 28 March 2018, 19:30:20 UTC
94ab26e jgraham 28 March 2018, 19:03:58 UTC fixup! Fix indentation 28 March 2018, 19:29:52 UTC
d79e8d2 Henrik Skupin 28 March 2018, 18:32:49 UTC Use detailed failure message for wdspec test failures (pytest). When adding failures to the test report, the hook for pytest_runtest_logreport missed to extract the failure message from the stack, and as such passed in no message for the failure. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1433923 gecko-commit: 849020c741de1e3bca2e22f5902e7d3b40f64ebd gecko-integration-branch: central gecko-reviewers: jgraham 28 March 2018, 19:29:52 UTC
c2707bb Henrik Skupin 28 March 2018, 18:49:31 UTC Find element for (partial) link text has to use rendered content. To retrieve links via "link text" or "partial link text" the rendered content of the element has to be used. This can be the case for CSS transformations like "uppercase". bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1381519 gecko-commit: 3e204686f1b10441f48435890241dff6706d04dd gecko-integration-branch: central gecko-reviewers: ato 28 March 2018, 19:09:49 UTC
42f4395 Henrik Boström 28 March 2018, 15:48:04 UTC RTCRtpSender.getStats() in blink added behind flag. This exposes RTCRtpSender.getStats() in JavaScript (behind flag) which implements the stats selection algorithm[1] for senders. [1] https://w3c.github.io/webrtc-pc/#dfn-stats-selection-algorithm Bug: 680172 Change-Id: I8117c87f475d1c78fa3301fc2d821f0c3a21281f Reviewed-on: https://chromium-review.googlesource.com/975306 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Harald Alvestrand <hta@chromium.org> Reviewed-by: Taylor Brandstetter <deadbeef@chromium.org> Cr-Commit-Position: refs/heads/master@{#546493} 28 March 2018, 15:58:25 UTC
f9c1a50 Rouslan Solomakhin 28 March 2018, 13:39:47 UTC Merge pull request #10203 from w3c/fixup_show_test fix: assert_equals check is wrong 28 March 2018, 13:39:47 UTC
cb4fe6c Rouslan Solomakhin 28 March 2018, 13:38:21 UTC Merge pull request #10204 from w3c/marcoscaceres-patch-1 Add @edenchuang again 🎊 28 March 2018, 13:38:21 UTC
e6cc359 Rouslan Solomakhin 28 March 2018, 13:37:44 UTC Merge pull request #10206 from w3c/marcoscaceres-patch-2 fix copy/pasta 28 March 2018, 13:37:44 UTC
2f758ac Anne van Kesteren 28 March 2018, 12:50:32 UTC DOM: reset target/relatedTarget For https://github.com/whatwg/dom/pull/585. 28 March 2018, 12:50:32 UTC
97d4646 Darren Shen 27 March 2018, 09:18:24 UTC [css-typed-om] Stub list-valued tests. Currently we're just adding a TODO when we want to test a list-valued property. It's probably easier if we stub that test function and then implement it later. Bug: 774887 Change-Id: Iab3cea915afbcc8490cacbd45e5632a18e7dece1 Reviewed-on: https://chromium-review.googlesource.com/981956 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#546067} 28 March 2018, 12:45:23 UTC
1d25beb Hayato Ito 28 March 2018, 12:08:08 UTC Keep track of all pending slot assignments, and recalc all before UpdateStyle phase For the purpose of rendering, Blink must calculate all pending slot assignments before UpdateStyle phase. Unless that, a recursive RecalcStyle() may not traverse a node which should be re-attached. e.g. Suppose the following tree, where #d1 is assigned to a slot. host ├──/shadow-root │ └── slot name=s1 └── div id=d1 slot=s1 Then, we change #d1's slot attribute to s2, like: > document.querySelector('#d1').setAttribute('slot', 's2'); host ├──/shadow-root │ └── slot name=s1 └── div id=d1 slot=s2 In this case, #d1 should be removed from a LayoutTree. In other words, Blink has to reattach #d1 somehow. However, if we don't recalc a slot assignment for the shadow tree before UpdateStyle, a recursive RecalcStyle never traverses the sub-tree because child-needs-style-recalc flag is not set for the node (and its ancestor nodes). A flag should be set as a result of slot assignment recalc. Thanks to the Incremental Shadow DOM, a slot assignemt recalc now becomes a local operatoin on each shadow tree, rather than one global operation for every shadow trees. We don't need to traverse a composed tree to recalc all. We can recalc a slot assignment for each shadow tree directly, without traversing a composed tree. For a shadow tree which is not connected, we don't need to recalc its slot assignment before UpdateStyle because such a shadow tree shouldn't have any effect on rendering. Lazy slot assignment recalc is enough for such a shadow tree. This CL doesn't introduce any optimization to minimize the number of to-be-reattached nodes. I'll optimize that as a next task. I'll use a sort of dynamic programming there, as I did at https://chromium-review.googlesource.com/c/chromium/src/+/535493 for non-Incremental Shadow DOM. Except for the performance, this CL should be the last part of Incremental Shadow DOM from the external behavior's perspective. Style and Layout should work correctly after this CL, even with Incremental Shadow DOM. BUG=776656 Change-Id: Id18e87ff59d92863c68c571e7db09253c08aa91f Reviewed-on: https://chromium-review.googlesource.com/964062 Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#546458} 28 March 2018, 12:17:59 UTC
6fca0b2 Kriti Singh 28 March 2018, 08:40:30 UTC Test that event handlers set on the window object are found on the body element (#10169) Based on event-handler-attributes-body-window.html. 28 March 2018, 08:40:30 UTC
3db7bb7 Hwanseung Lee 28 March 2018, 06:47:36 UTC [css-typed-om] support x, y, cx, cy properties x[1], y[2], cx[3], cy[4] are added to support in whitelist. and test file are also added. [1]https://svgwg.org/svg2-draft/geometry.html#X [2]https://svgwg.org/svg2-draft/geometry.html#Y [3]https://svgwg.org/svg2-draft/geometry.html#CX [4]https://svgwg.org/svg2-draft/geometry.html#CY Bug: 820299 Change-Id: I46ced4427a5e7b2e08aa132fc0b8c5d2e1f19d22 Reviewed-on: https://chromium-review.googlesource.com/983077 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#546426} 28 March 2018, 07:07:27 UTC
67ae39c Marcos Cáceres 28 March 2018, 06:12:01 UTC fix copy/pasta 28 March 2018, 06:12:01 UTC
e343b5d Marcos Cáceres 28 March 2018, 03:52:58 UTC Add @edenchuang again 🎊 28 March 2018, 03:52:58 UTC
4b535ba Marcos Cáceres 28 March 2018, 03:39:52 UTC fix: assert_equals check is wrong 28 March 2018, 03:39:52 UTC
383fd73 Kinuko Yasuda 28 March 2018, 01:47:22 UTC Re-land: "Don't adjust the NavigationTimings on redirects" The reason for revert was the new navigation timing test expectations (that got commited right before the original change) had a FAIL expectation for the particular event order that this change was fixing. Original change's description: > Don't adjust the NavigationTimings on redirects > > We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), > shouldn't update in each AddRedirect() (which is called in a batch > way after all the redirects are handled in the browser process with PlzNavigate, > adjusting timings there with current timestamp is totally wrong) > > R=​ksakamoto,arthursonzogni > > Bug: 813889 > Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b > Reviewed-on: https://chromium-review.googlesource.com/974673 > Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> > Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#546001} Bug: 813889 Change-Id: I6f5c0ba1196fa1dd52225036820b29a95569ac21 Reviewed-on: https://chromium-review.googlesource.com/981913 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#546365} 28 March 2018, 02:06:24 UTC
62d7010 Darren Shen 28 March 2018, 01:47:15 UTC [css-typed-om] Support some text-decoration properties. Adds tests for: - text-decoration - text-decoration-line - text-decoration-skip (not implemented in Blink) - text-decoration-skip-ink - text-decoration-width (not implemented in Blink) text-decoration-line uses a weird internal structure for CSSValues, so we have to encode/decode to that structure when getting/setting. Failing tests because for some reason we ignore 'blink' for the computed value. Blink also doesn't support 'spelling-error' and 'grammar-error' yet. Bug: 820299 Change-Id: I60e8c3958c9b3a784177c9813a7325aa26e39581 Reviewed-on: https://chromium-review.googlesource.com/981717 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#546364} 28 March 2018, 01:58:10 UTC
45d92eb Hwanseung Lee 27 March 2018, 23:07:16 UTC [css-typed-om] support r and rx and ry properties r[1], rx[2], ry[3] are added to support in whitelist. and test file are also added. [1]https://svgwg.org/svg2-draft/geometry.html#R [2]https://svgwg.org/svg2-draft/geometry.html#RX [3]https://svgwg.org/svg2-draft/geometry.html#RY Bug: 820299 Change-Id: I51457648ca07aaf06cf15bd28452d5ad8099d2e3 Reviewed-on: https://chromium-review.googlesource.com/981918 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#546302} 27 March 2018, 23:16:32 UTC
8ccaab2 Hiroki Nakagawa 27 March 2018, 21:19:33 UTC Worker: Add tests for import.meta.url on DedicatedWorker Bug: 680046 Change-Id: Ieb341c5922ad247961ca477893037896dbd88ea6 Reviewed-on: https://chromium-review.googlesource.com/974726 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#546254} 27 March 2018, 21:32:08 UTC
8214a83 Stephen McGruer 27 March 2018, 18:33:18 UTC Port nested sticky tests from reftests to JS tests Bug: 699244 Change-Id: Ia85a44be9d9f7b0d0db382892520f2755523f514 Reviewed-on: https://chromium-review.googlesource.com/980236 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#546172} 27 March 2018, 18:53:44 UTC
e96e038 Rouslan Solomakhin 27 March 2018, 14:27:09 UTC Merge pull request #10180 from rsolomakhin/method Replace 'enabledMethods' array with 'method' string. 27 March 2018, 14:27:09 UTC
6135f17 Rune Lillesveen 27 March 2018, 12:06:44 UTC [css-typed-om] Add support for the column-width property. Bug: 820299 Change-Id: I9e380416b18f30294fe7cb969a0ce7d0ab1fd7bd Reviewed-on: https://chromium-review.googlesource.com/977910 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#546082} 27 March 2018, 12:15:41 UTC
2e48036 Ben Wells 27 March 2018, 05:42:26 UTC Revert "Don't adjust the NavigationTimings on redirects" This reverts commit aeecb4f32ece14a8a294e4f9b80a5bb2278091c9. Reason for revert: Causing lots of failures on webkit bots, e.g.: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty/42143 Original change's description: > Don't adjust the NavigationTimings on redirects > > We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), > shouldn't update in each AddRedirect() (which is called in a batch > way after all the redirects are handled in the browser process with PlzNavigate, > adjusting timings there with current timestamp is totally wrong) > > R=​ksakamoto,arthursonzogni > > Bug: 813889 > Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b > Reviewed-on: https://chromium-review.googlesource.com/974673 > Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> > Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#546001} TBR=kinuko@chromium.org,ksakamoto@chromium.org,arthursonzogni@chromium.org Change-Id: I467ed888084ea0eda06faa903d1797fabffc47da No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 813889 Reviewed-on: https://chromium-review.googlesource.com/981912 Reviewed-by: Ben Wells <benwells@chromium.org> Commit-Queue: Ben Wells <benwells@chromium.org> Cr-Commit-Position: refs/heads/master@{#546025} 27 March 2018, 06:03:29 UTC
8ec345b Ian Kilpatrick 27 March 2018, 05:07:50 UTC [css-layout-api] Allow developers to position fragments. This implements the LayoutFragment.inlineOffset and LayoutFragment.blockOffset attributes. The tests added simply re-create the reference by setting these two attributes in different text directions and writing modes. Change-Id: I1865403ca12e3b174738ee93320eae5ba16ac292 Bug: 726125 Reviewed-on: https://chromium-review.googlesource.com/971832 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#546018} 27 March 2018, 05:15:10 UTC
c32afde Kinuko Yasuda 27 March 2018, 04:00:12 UTC Don't adjust the NavigationTimings on redirects We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), shouldn't update in each AddRedirect() (which is called in a batch way after all the redirects are handled in the browser process with PlzNavigate, adjusting timings there with current timestamp is totally wrong) R=ksakamoto,arthursonzogni Bug: 813889 Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b Reviewed-on: https://chromium-review.googlesource.com/974673 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#546001} 27 March 2018, 04:09:22 UTC
9246170 Kenichi Ishibashi 27 March 2018, 03:21:32 UTC service_worker: Add tests for navigation timing This CL adds some tests for PerformanceNavigationTiming which are involved with service worker. - SW intercepts a navigation - SW falls back to network - Redirect and SW intercepts a navigation These tests check `workerStart <= fetchStart` because starting a worker should happen before fetching a resource when service worker is involved. Bug: 782958 Change-Id: Idd3fa8f76a328e77ee531b81bd91ee3db223f12c Reviewed-on: https://chromium-review.googlesource.com/979873 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#545935} 27 March 2018, 03:30:28 UTC
06f77f6 Rune Lillesveen 27 March 2018, 00:22:42 UTC [css-typedom] Add support for the *-gap properties. Bug: 820299 Change-Id: I596113eeea7d4c13cf689364744bff7c261f93d3 Reviewed-on: https://chromium-review.googlesource.com/978247 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545896} 27 March 2018, 00:31:06 UTC
f497de8 Robert Ma 26 March 2018, 20:24:51 UTC Better explain test execution in resources/test/README 26 March 2018, 21:12:14 UTC
7988e17 Ian Kilpatrick 26 March 2018, 18:44:58 UTC [css-layout-api] Allow LayoutChild(ren) to be laid out. This allows a LayoutChild to have layout performed on it, which will return a Fragment - with the correct inline and block sizes. These Fragments cannot be positioned yet, (next patch). The LayoutChild will be laid out with an available inline/block size of zero by default, and optionally can accept a fixed-inline/block size, which it must respect. Bug: 726125 Change-Id: Ie4386b8f6cd6ccec3f9e52ff332322101058836d Reviewed-on: https://chromium-review.googlesource.com/962870 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#545845} 26 March 2018, 19:34:57 UTC
a35b824 Boris Zbarsky 26 March 2018, 18:16:29 UTC part 3. Add testing for what mutation observers happen when doing DOMTokenList.replace. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1444909 gecko-commit: bb405d71ba671812bddc20aaa935f1a2bbe53499 gecko-integration-branch: central gecko-reviewers: qdot 26 March 2018, 18:37:35 UTC
5957997 fantasai 07 February 2018, 00:55:57 UTC [css-sizing-3] Add tests for intrinsic size contribution (width/inline-size) of non-replaced blocks with percentage widths. See https://github.com/w3c/csswg-drafts/issues/1132 26 March 2018, 18:13:34 UTC
c5e2e61 Rouslan Solomakhin 26 March 2018, 16:27:36 UTC Replace 'enabledMethods' array into 'method' string. 26 March 2018, 16:27:36 UTC
a890989 Hwanseung Lee 26 March 2018, 15:54:44 UTC [css-typed-om] support block-size and inline-size block-size[1], inline-size[2], max-block-size[3], max-inline-size[4], min-block-size[5], min-inline-size[6] are added to support in whitelist. and test file are also added. [1]https://drafts.csswg.org/css-logical-1/#propdef-block-size [2]https://drafts.csswg.org/css-logical-1/#propdef-inline-size [3]https://drafts.csswg.org/css-logical-1/#propdef-max-block-size [4]https://drafts.csswg.org/css-logical-1/#propdef-max-inline-size [5]https://drafts.csswg.org/css-logical-1/#propdef-min-block-size [6]https://drafts.csswg.org/css-logical-1/#propdef-min-inline-size Bug: 820299 Change-Id: I97c589deea28bfedc82ec1b1686ceaf9979cb95e Reviewed-on: https://chromium-review.googlesource.com/973561 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545802} 26 March 2018, 16:03:03 UTC
3b57b11 Josh Matthews 26 March 2018, 14:23:24 UTC Add base protocol to ConnectionlessProtocol. 26 March 2018, 14:47:13 UTC
f4388a3 Morten Stenshorne 26 March 2018, 14:00:45 UTC [css-flexbox] Resolve min-width:auto on table item to min preferred size. Edge and Firefox seem to let table flex items use the sizing algorithm of the table extensively, and are therefore generally broken when it comes to flexing tables. We, on the other hand, let the flex sizing algorithm be in charge of sizing tables, so that flexing actually works. However, this causes tables with a specified main size of less than the minimum intrinsic logical width of the table to shrink below their minimum intrinsic logical width, a situation that's generally unwanted for tables. Amend by ignoring the specified main size when resolving min-width:auto on table items. Also ignore max-width/max-height. Just use the preferred minimum logical width. Bug: 821832 Change-Id: I78ca0c8e0041ea69bb606ff72d340bb3f5f9bb96 Reviewed-on: https://chromium-review.googlesource.com/964203 Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#545777} 26 March 2018, 14:10:13 UTC
ff4fae1 Chandan Padhi 26 March 2018, 10:09:55 UTC Add support for autoGainControl and noiseSuppression to getCapabilities() This CL adds support for autoGainControl and noiseSuppression properties to MediaStreamTrack.getCapabilities() and InputDeviceInfo.getCapabilities(). Bug: 823831, 817769 Change-Id: Ifdc0e560001e000b12c8d04634d3c52de0a34cc7 Reviewed-on: https://chromium-review.googlesource.com/977251 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Chandan Padhi <c.padhi@samsung.com> Cr-Commit-Position: refs/heads/master@{#545750} 26 March 2018, 10:19:04 UTC
e31f590 Hiroki Nakagawa 26 March 2018, 09:29:42 UTC Worker: Allow dynamic import() on DedicatedWorkerGlobalScope This CL allows dynamic import() on DedicatedWorkerGlobalScope and adds WPT tests. Note that ES Modules on DedicatedWorker is an experimental feature behind the runtime flag. Design doc: https://docs.google.com/document/d/1IMGWAK7Wq37mLehwkbysNRBBnhQBo3z2MbYyMkViEnY/edit#heading=h.637avx8i5qtn Bug: 680046 Change-Id: I1f8fed5c319aab634f96bcfabeb3c95f5dc7d9a7 Reviewed-on: https://chromium-review.googlesource.com/970127 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#545748} 26 March 2018, 09:37:45 UTC
4ff4c66 Darren Shen 26 March 2018, 01:54:20 UTC [css-typed-om] Support font properties. We try to support as many font properties as possible. However, several font properties have not been implemented in Blink yet. Also, the computed value for font-stretch is wrong (it should be as specified, and no rounding should occur). Spec: https://drafts.css-houdini.org/css-typed-om-1/#reify-stylevalue Bug: 820299 Change-Id: I744d03a08856bd6d0df6bd07230ec80138e6e3b7 Reviewed-on: https://chromium-review.googlesource.com/977247 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545721} 26 March 2018, 02:10:55 UTC
d04a8fc Robert Ma 23 March 2018, 22:18:18 UTC Fix some IDL tests after html.idl includes SVGElement html.idl changed in upstream https://github.com/w3c/web-platform-tests/pull/10110 and imported in https://crrev.com/c/978021 Bug: 825191 Change-Id: Ie1a04e730aabd50c615f1dab079f92eeaa22565a Reviewed-on: https://chromium-review.googlesource.com/978508 Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#545588} 23 March 2018, 22:37:33 UTC
7991f4b Ovidio Henriquez 23 March 2018, 17:54:47 UTC bluetooth: Impl. setNextWriteResponse (descriptor) Also implements getLastWrittenValue() and converts two tests to use these. FakeRemoteGattDescriptor::setNextWriteResponse allows tests to set the next response for a write. BUG=719825 Change-Id: I2807d23a55f79eeca35338e25916c6d5e0115e89 Reviewed-on: https://chromium-review.googlesource.com/964901 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Cr-Commit-Position: refs/heads/master@{#545508} 23 March 2018, 18:32:09 UTC
af184df youennf 23 March 2018, 17:40:23 UTC Merge pull request #10151 from youennf/wpt-export-for-webkit-183928 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=183928 23 March 2018, 17:40:23 UTC
273bb41 Ovidio Henriquez 23 March 2018, 15:12:10 UTC bluetooth: Add RemoveFakeDescriptor to BT test This change allows the removal of a descriptor to be simulated by the Bluetooth test interface. A generated test script was also converted to test the new interface. BUG=569709 Change-Id: Id4286a3e44cd04ee1b371938f1ef89f33458269c Reviewed-on: https://chromium-review.googlesource.com/972334 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Conley Owens <cco3@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#545448} 23 March 2018, 15:30:21 UTC
2d1fd9e Rune Lillesveen 23 March 2018, 14:59:20 UTC Don't skip display:none options finding selectable options. This means we can also assume a null ComputedStyle on options means they are display:none. That is a pre-requisite for fixing issue 822581. Bug: 824754 Change-Id: Ia8a400ec8eed9ecb9a85d2c93c354841ad721492 Reviewed-on: https://chromium-review.googlesource.com/975604 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545443} 23 March 2018, 15:12:06 UTC
a1ec330 Blink WPT Bot 23 March 2018, 14:42:53 UTC PaymentRequest: Use [SecureContext] instead of manual check (#8648) Until now, we had to use IsSecureContext() to check whether an execution context is a secure context manually. But we can use [SecureContext] instead of the manual check now. After this change, all related APIs including PaymentRequest will not be exposed in non-secure context. Bug: none Change-Id: Ie5b3fc6641e882cc2844595fea350b6adb3425db 23 March 2018, 14:42:53 UTC
4578f69 Luke Bjerring 23 March 2018, 13:37:57 UTC idlharness.js: Distinguish instance toJSON is being executed against when it's inherited (#10029) * Distinguish which instance toJSON is being executed against when inherited 23 March 2018, 13:37:57 UTC
b705dc1 Ahilya Sinha 23 March 2018, 13:09:14 UTC Fixed lint checking directories it shouldn't be (#10147) Lint earlier checked _venv/ and .git/ which it shouldn't be checking. 23 March 2018, 13:09:14 UTC
174f764 jgraham 23 March 2018, 12:27:05 UTC Fix python gitignore for directories. (#10131) For top level directories like _venv/ we were creating the regexp ^\_venv/$, which we were then feeding paths like _venv/bin/foo which it fails to match. Since we are matching against full paths, we certainly want to allow matching _venv/* and probably also bare _venv, so add a special case for paths with a trailing slash to allow these options. 23 March 2018, 12:27:05 UTC
9e2e5eb Sergio Villar Senin 23 March 2018, 11:33:30 UTC [css-grid] Fix auto repeat tracks computation with definite min sizes Indefinitely sized containers use the specified definite min-size (if any) as available space in order to compute the number of auto repeat tracks to create. A bug in that code was causing the grid to be one track larger than expected. That was only happening in the case of the free space being a multiple of the total size of the autorepeat tracks. Bug: 823140 Change-Id: I6cc13df478da4ba00585fa557012391291941d1a Reviewed-on: https://chromium-review.googlesource.com/973522 Commit-Queue: Sergio Villar <svillar@igalia.com> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#545403} 23 March 2018, 11:41:52 UTC
b04a923 Michael[tm] Smith 23 March 2018, 10:42:57 UTC cc Update messages.json 23 March 2018, 10:57:43 UTC
20d739e Anne van Kesteren 20 March 2018, 14:55:59 UTC Add HTMLOrSVGElement to HTML's IDL And align a couple other things while there. Helps with https://github.com/whatwg/html/pull/3543. 23 March 2018, 10:24:48 UTC
48d50c6 Youenn Fablet 23 March 2018, 05:15:23 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=183928 23 March 2018, 05:15:23 UTC
e40c752 Marcos Cáceres 23 March 2018, 03:37:07 UTC Tests for PaymentItem.type member (#9099) 23 March 2018, 03:37:07 UTC
4e1bb51 Xianzhu Wang 22 March 2018, 20:37:21 UTC [PE] Add ToInt() for logical padding top and bottom for LayoutTableCell This reverts the logic for logical top/bottom paddings to be the same as before https://chromium-review.googlesource.com/619603. The logical top/bottom paddings are truncated like what we do for other table layouts. We still keep subpixels for logical left/right paddings to ensure correct logical width calculation. This is still the same as before https://chromium-review.googlesource.com/619603. Bug: 823824 Change-Id: Icb617bf5771d1726f767207853f4adc8275731dc Reviewed-on: https://chromium-review.googlesource.com/974315 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#545225} 22 March 2018, 20:49:19 UTC
9dcebcb Robert Ma 22 March 2018, 19:02:06 UTC Add .tox to global .gitignore 22 March 2018, 20:18:25 UTC
f94a28a Robert Ma 21 March 2018, 17:35:46 UTC Fix resources/test (when running locally) 1. Check the HTTP port of wptserve instead of HTTPS to avoid the unnecessary complexities of setting up SSL context (which may fail in some environments). 2. Use exponential backoff when waiting for wptserve and specify a maximum retry to avoid indefinite hang. 3. Use `terminate` instead of `kill` to give wptserve a chance to clean up, which is especially useful when running locally. WPTServe.url still returns a HTTPS URL to make sure tests that require secure context (e.g. service workers) still work. 22 March 2018, 20:18:25 UTC
df2e803 Luke Bjerring 22 March 2018, 19:15:29 UTC Handle options for add_untested_idls (#10100) 22 March 2018, 19:15:29 UTC
e48a42f Harald Alvestrand 22 March 2018, 18:59:43 UTC Add memory of last SDP offer/answer created This adds internal slots "LastOffer" and "LastAnswer", and uses those to check that SetLocalDescription uses an unchanged SDP offer/answer. Because modification of SDP is suspected to be used in a number of places, this change only rejects SDP with modified fingerprints (which would fail anyway), but merely counts the usage for other modifications. Bug: chromium:823036 Change-Id: I0c978d5ff3e63b0afab3ec02334c57a5aaa94cdd Reviewed-on: https://chromium-review.googlesource.com/966441 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Tommi <tommi@chromium.org> Cr-Commit-Position: refs/heads/master@{#545175} 22 March 2018, 19:10:10 UTC
99914e1 Hayato Ito 22 March 2018, 09:56:30 UTC Reject customized built-in elements in attachShadow Element::CanAttachShadowRoot() needs to be updated because it returns wrongly true for customized built-in elements. The spec: https://dom.spec.whatwg.org/#dom-element-attachshadow Bug: 823033 Change-Id: Ia9aeb47569414830f5435f37f85d96101b9fe432 Reviewed-on: https://chromium-review.googlesource.com/970142 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#545026} 22 March 2018, 10:06:31 UTC
74126cb Frédéric Wang 22 March 2018, 07:57:21 UTC MathML: Test italic correction of sub and super scripts attached to a large operator (#9993) 22 March 2018, 07:57:21 UTC
5ffa505 Joe Downing 22 March 2018, 07:35:35 UTC Move KeyboardLock API methods to a 'keyboard' object This change moves the KeyboardLock API methods to a 'keyboard' namespace on the Navigator object. We are doing this work now as there has been a request for additional keyboard functionality that would also be placed on the new keyboard object and we wanted to move the KeyboardLock methods there for consistency before we launch. KeyboardLock API Spec is here: https://w3c.github.io/keyboard-lock/#API Old calling pattern: Navigator.keyboardLock(); Navigator.keyboardUnlock(); New calling pattern: Navigator.keyboard.lock(); Navigator.keyboard.unlock(); Note: The main logic in the KeyboardLock.cpp class and tests is the same as it was, however the file changed enough that git does not recognize it as a file move. BUG=680809 Change-Id: I234b2ab12d5ecd44c894ed5103863fd96fd548d4 Reviewed-on: https://chromium-review.googlesource.com/969656 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#544996} 22 March 2018, 07:45:48 UTC
1a8c195 Hiroki Nakagawa 22 March 2018, 05:53:36 UTC Worker: Support ES Modules on DedicatedWorker behind the runtime flag This CL supports ES Modules on DedicatedWorker behind the ModuleDedicatedWorker flag and adds WPT tests. With the flag, you can specify 'type' option on the constructor of DedicatedWorker (i.e., new Worker) to start a dedicated worker as a module script. On DedicatedWorkerGlobalScope, static import is available, but dynamic import() hasn't been implemented yet. Bug: 680046 Change-Id: I3aca350228ec07be7884c7a2eb8cd351e7fd6b6e Reviewed-on: https://chromium-review.googlesource.com/967908 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#544983} 22 March 2018, 06:21:57 UTC
14f1aec Yoshifumi Inoue 22 March 2018, 04:00:01 UTC Make Range::intersectsNode() to follow the spec This patch change |Range::intersectsNode()| to follow the spec[1]. [1] https://dom.spec.whatwg.org/#dom-range-intersectsnode Bug: 822510 Change-Id: Ifd504443355da12482b759701cddd62e2a90d7a6 Reviewed-on: https://chromium-review.googlesource.com/970044 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#544971} 22 March 2018, 04:10:17 UTC
f5b48cf Marcos Cáceres 22 March 2018, 02:27:28 UTC Prevent false positives (#10120) 22 March 2018, 02:27:28 UTC
405e0e9 Rune Lillesveen 22 March 2018, 01:57:52 UTC [css-typed-om] Add support for column-span. Reify as an identifier. Bug: 820299 Change-Id: I483a1e3c126e5b280a2337772584070f96cd533e Reviewed-on: https://chromium-review.googlesource.com/970263 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#544939} 22 March 2018, 02:08:04 UTC
0529cde Luke Bjerring 22 March 2018, 01:33:12 UTC Update web-animations IDL file (#9908) 22 March 2018, 01:33:12 UTC
26e8a76 Nicolás Peña 21 March 2018, 23:20:26 UTC Move remaining Intel/resource-timing/ tests to WPT Bug: 498037 Change-Id: I8f0e72da2aac76e5ff8ac0b4ffffd8b228e0ac42 Reviewed-on: https://chromium-review.googlesource.com/970047 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#544895} 21 March 2018, 23:40:53 UTC
3c0e03d Marijn Kruisselbrink 21 March 2018, 22:30:54 UTC [Blobs] Correctly set mimetype of blob in FetchDataLoader. Just creating a new BlobDataHandle doesn't actually update the mimetype of the blob (if later the blob is requested through a blob: URL for example), so instead actually create a new blob wrapping the existing blob to properly change the mimetype. Bug: none Change-Id: I93b6d584178a02a74d68bdd6fcace1514ca90ec0 Reviewed-on: https://chromium-review.googlesource.com/967271 Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#544864} 21 March 2018, 22:40:16 UTC
b1ef882 Harald Alvestrand 21 March 2018, 19:52:04 UTC Test that DTMFSender rejects properly after close This verifies that the sender throws the right error when called after the connection closing. Bug: chromium:822799 Change-Id: Id3ab4ddc65b1510526fa49b7bfe3f9f95a7f2d65 Reviewed-on: https://chromium-review.googlesource.com/968927 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#544804} 21 March 2018, 20:03:53 UTC
c6ed739 Sandra Sun 21 March 2018, 19:01:15 UTC Implement scroll-snap-type: proximity As specified in the spec, when the snap-container has scroll-snap-type: proximity, we should only consider snap positions that are close to the current scroll offset. https://drafts.csswg.org/css-scroll-snap-1/#snap-strictness Bug: 823820 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I6312f98df421e303eb538f422ede39cea8dd5d38 Reviewed-on: https://chromium-review.googlesource.com/971466 Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Reviewed-by: Ali Juma <ajuma@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#544783} 21 March 2018, 19:12:40 UTC
888f7df Chris Harrelson 21 March 2018, 17:47:30 UTC Make <foreignObject> a stacking context. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DHSUFGpZafc Bug: 723076 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I09d422e0fa9888610cfb3a8acfcea6c9f8c8de24 Reviewed-on: https://chromium-review.googlesource.com/831397 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#544756} 21 March 2018, 18:19:40 UTC
dbb38a6 Luke Bjerring 21 March 2018, 15:20:29 UTC Update storage idl file (#9833) 21 March 2018, 15:20:29 UTC
5edf4f2 Luke Bjerring 21 March 2018, 14:49:08 UTC Update the webvtt IDL file (#9855) * Add webvtt idl file * Update webvtt/api/interfaces.html to use IDL 21 March 2018, 14:49:08 UTC
b873ed6 Luke Bjerring 21 March 2018, 14:02:28 UTC Update the css-typed-om IDL file (#9775) * Update css-typed-om IDL * Re-introduce commenting of CSS namespace 21 March 2018, 14:02:28 UTC
ab293a5 Luke Bjerring 21 March 2018, 13:59:57 UTC Update payment-request IDL file (#9797) 21 March 2018, 13:59:57 UTC
535e962 Manuel Rego Casasnovas 21 March 2018, 13:42:37 UTC [css-grid] Fix testing-utils.js We have been calling testGridTemplateColumnsRows() with and without arrays. Arrays are needed because the serialization of 2 tracks of the same size can be "100px 100px" or "repeat(2, 100px)". But in the rest of the cases we don't need an array, so we call the method with a single value. testGridTemplateColumnsRows() was not ready to support that, and it wasn't actually checking anything in that case. The patch modifies testing-utils.js, so it wraps values in an array when required. Now testGridTemplateColumnsRows() will be actually checking things. Change-Id: I7e360677c391df74dedb474922bf5c04247141c5 Reviewed-on: https://chromium-review.googlesource.com/973063 Reviewed-by: Sergio Villar <svillar@igalia.com> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#544681} 21 March 2018, 13:53:19 UTC
47c9322 Robert Ma 21 March 2018, 13:45:02 UTC Attempt to fix ci_resources_unittest (#10116) The test wasn't running against the downloaded Firefox Nightly but system Firefox instead, which is fixed by passing the binary path to tox (which then passes it to pytest conftest.py). The pip requirements should be managed by tox. 21 March 2018, 13:45:02 UTC
fc04bb5 Anne van Kesteren 21 March 2018, 08:38:11 UTC Test postMessage() exception order For https://github.com/whatwg/html/pull/3508 and https://github.com/whatwg/html/pull/3557. 21 March 2018, 08:38:11 UTC
f8920ff Marcos Cáceres 21 March 2018, 03:46:47 UTC Edge doesn't do object spread yet (#10119) 21 March 2018, 03:46:47 UTC
92885ac Marcos Cáceres 21 March 2018, 01:49:00 UTC user activation must survive postMessage() to call show() (#10090) Check that we can call pr.show() in an iframe via postMessage(), which is triggered by user activation. 21 March 2018, 01:49:00 UTC
66e0742 Wanming Lin 21 March 2018, 01:29:05 UTC Revert "rename generic-sensor directory as sensors" (#10068) 21 March 2018, 01:29:05 UTC
3a83284 Robert Ma 20 March 2018, 18:52:04 UTC Address comments * Renaming `check_stability.run` breaks commands.json and naming conventions, so rename the other `run` in that module instead. * Only return errors for empty results when we know for sure tests are affected. 20 March 2018, 20:32:14 UTC
7e214e8 Robert Ma 19 March 2018, 15:34:37 UTC Exit check_stability with an error when no tests run Similar to #10030 (which was for `wpt run`), this commit makes `wpt check-stability` return a non-zero exit code when no tests run. Also fix some code smells: * `run` was redefined by `do_delayed_imports` to a different function. Rename the other `run` method in this module to `setup_and_run`. * `retcode` was unnecessarily defined in the top scope. Remove it to avoid redefinition. * `global logger` and the call to `get_parser` were extraneous in `run` (now `setup_and_run`) and hence are removed. 20 March 2018, 20:32:14 UTC
4d10320 Robert Ma 16 March 2018, 21:17:56 UTC No longer allow Chrome stability check to fail After #10064, Chrome jobs run successfully on Travis, so we can turn the stability check back on. Fixes #9932. 20 March 2018, 19:02:42 UTC
dacfb44 Joshua Bell 20 March 2018, 17:58:31 UTC Indexed DB: Consolidate window/worker IDL tests into any.js Also, rely on HTML and DOM interfaces for dependencies rather than inline definitions for Event, EventTarget, etc. Change-Id: I58ac6515f8d2769aec6bbf1b90d9a4105639ad24 Reviewed-on: https://chromium-review.googlesource.com/965452 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#544429} 20 March 2018, 18:25:58 UTC
e04e71f Kriti Singh 20 March 2018, 17:57:36 UTC Stop using wrappedJSObject in marionette executor (#10041) 20 March 2018, 17:57:36 UTC
6e1b5f4 Mattias Buelens 20 March 2018, 13:27:09 UTC ReadableStream: Readable byte stream must call pull if needed after receiving new chunk (#10018) * Fix test that allows too much pulling * Test that byte stream pulls after enqueue 20 March 2018, 13:27:09 UTC
31c11a7 Luke Bjerring 20 March 2018, 13:10:20 UTC Update the web-share IDL file (#9843) 20 March 2018, 13:10:20 UTC
f2ae764 Adam Rice 20 March 2018, 12:30:43 UTC Correctly reject in-progress body methods with AbortError Prior to this change, response body methods such as response.body.arrayBuffer() would reject with a TypeError if the fetch was aborted. This change makes them correctly reject with an AbortError instead. This implements stage #3 of the "Body Cancellation" section of the design doc: https://docs.google.com/document/d/1OuoCG2uiijbAwbCw9jaS7tHEO0LBO_4gMNio1ox0qlY/edit#heading=h.fvc7d7q07oio Bug: 817687 Change-Id: Ifde322d9c22485a8ba9d14fd4ffca65c4fb4745a Reviewed-on: https://chromium-review.googlesource.com/954765 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#544335} 20 March 2018, 12:38:49 UTC
7cb5db5 Emilio Cobos Álvarez 20 March 2018, 02:29:00 UTC Make Shadow DOM account for stylesheet applicableness correctly. Summary: Also, make stuff sound in presence of CSSOM and what not. The dirty: false thing is reverting an accidental change that landed in the de-XBL stuff, which was harmless, but now wouldn't let me assert stuff properly. Reviewers: xidorn Bug #: 1445682 Differential Revision: https://phabricator.services.mozilla.com/D748 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1445682 gecko-commit: f2149d69f47cd9e7a2d0b478c2c63cb020dbfda9 gecko-integration-branch: central gecko-reviewers: xidorn 20 March 2018, 02:40:51 UTC
back to top