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
7d92dbd Mike West 06 December 2018, 10:19:53 UTC Trusted Types: URLs should be USVString, not DOMString. This patch adjusts `ScriptURLString` to be a union including `USVString`, not `DOMString`. The advice in [WebIDL][1] isn't exactly clear, but it boils down to @domenic's notes in [heycam/webidl#84][2] and [w3ctag/design-principles#93][3]. Long story short, URLs are `USVString`. This patch adjusts our implementation to match. [1]: https://heycam.github.io/webidl/#idl-USVString [2]: https://github.com/heycam/webidl/issues/84#issuecomment-300857185 [3]: https://github.com/w3ctag/design-principles/issues/93#issuecomment-379816152 Change-Id: I9bf1240b421287d7d9c291b13d887ca981a66231 06 December 2018, 10:19:53 UTC
93af5d9 autofoolip 06 December 2018, 09:17:28 UTC Update interfaces/web-nfc.idl (#14388) Source: https://github.com/tidoust/reffy-reports/blob/1c79dd7/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/464203271 06 December 2018, 09:17:28 UTC
4bdeca6 Philip Jägenstedt 06 December 2018, 09:13:53 UTC Tests for SVG tabindex/focus/blur (#10149) * Add test for SVG focus flag * Update focus-flag test * Add test for default tabIndex value Adapted from html/editing/focus/sequential-focus-navigation-and-the-tabindex-attribute/focus-tabindex-default-value.html * Add focus management test Adapted from HTML version at /html/editing/focus/focus-management/focus-events.html * Add focus composed test Based on HTML's composed.window.js * Respond to feedback Remove test for audio/video without controls and add non root svg 06 December 2018, 09:13:53 UTC
0d02fc9 Frédéric Wang 05 December 2018, 15:50:09 UTC Add link to CSS Overscroll behavior spec. 06 December 2018, 09:12:20 UTC
6608f66 Frédéric Wang 05 December 2018, 11:28:05 UTC Move overscrollBehavior-manual.html into css/css-overscroll-behavior This property does not belong to the CSSOM View spec. 06 December 2018, 09:12:20 UTC
0347da3 autofoolip 06 December 2018, 08:56:39 UTC Update interfaces/event-timing.idl (#14387) Source: https://github.com/tidoust/reffy-reports/blob/1c79dd7/whatwg/idl/event-timing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/464203271 06 December 2018, 08:56:39 UTC
3e60f8f Matt Falkenhagen 06 December 2018, 05:42:55 UTC WPT: service worker: fix test for CSS base URL. The existing test was asserting the opposite of the standard, which is to use the response URL. See https://github.com/whatwg/fetch/pull/146. This CL does the following: - Tests that a CSS stylesheet fetched via respondWith(fetch(responseUrl) uses responseUrl as its base URL. - Tests that a CSS stylesheet fetched via respondWith(new Response()) uses the response URL (which is the request URL) as its base URL. - Changes the test to not test cross-origin stylesheets. That is more complex than needed for this test, and there is talk of making subresource requests from opaque stylesheets skip the service worker, which would render the test ineffective for testing base URL. - Changes the test to use waitUntil() in the message event to try to ensure the service worker stays alive between the message and fetch events. Bug: 911974 Change-Id: I167dfe86986ec718a50d512f862f1eb49889608b Reviewed-on: https://chromium-review.googlesource.com/c/1362776 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#614277} 06 December 2018, 05:52:00 UTC
ee3ec2e Tim Haloun 06 December 2018, 01:56:20 UTC web platform tests for new networkPriority encoding parameter. Bug: webrtc:5008 Change-Id: I867b0811917f0356f05417f6186124d92c3a0622 Reviewed-on: https://chromium-review.googlesource.com/c/1357515 Commit-Queue: Tim Haloun <thaloun@chromium.org> Reviewed-by: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#614228} 06 December 2018, 02:05:12 UTC
093a97b Koji Ishii 05 December 2018, 22:23:08 UTC [LayoutNG] Fix when `break-word` is applied to inline boxes This patch fixes NGLineBreaker when `break-word` is applied to inlne boxes. It works properly only when `break-word` is applied to containing block before this fix. To fix this, NGInlineItemResult keeps the value of `break_anywhere_if_overflow` for each item. Change-Id: I6e51ffa31a015f0e2ba82f536982a912424b9eba Bug: 902659 Reviewed-on: https://chromium-review.googlesource.com/c/1355310 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#614125} 05 December 2018, 22:32:04 UTC
796c622 youennf 05 December 2018, 21:10:34 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=189727 (#14369) 05 December 2018, 21:10:34 UTC
5781139 Eric Willigers 05 December 2018, 20:06:21 UTC SVG Painting: computed property values (#14211) * SVG Painting: computed property values Keyword values are as specified. Lengths are converted to absolute lengths. Urls are converted to absolute paths. Found bug: https://bugs.chromium.org/p/chromium/issues/detail?id=908058 *-opacity should be clamped to [0,1] 05 December 2018, 20:06:21 UTC
8dacc52 Eric Willigers 05 December 2018, 20:02:48 UTC SVG property parsing with CSS length units (#14367) Test all the length units defined in CSS Values and Units Module Level 3 https://www.w3.org/TR/css-values-3/#lengths are parsed successfully in SVG properties. 05 December 2018, 20:02:48 UTC
31e51c5 Roger McFarlane 05 December 2018, 18:10:58 UTC [Sheriff] Revert "Don't estimate the top of bottom-aligned OOFs as bottom." This reverts commit d5096cb8a5d544acb51f8b4df908775b6584778f. Reason for revert: This looks like a likely culprit breaking WebKit Win10 printing/absolute-position-headers-and-footers.html virtual/threaded/printing/absolute-position-headers-and-footers.html https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Win10 Original change's description: > Don't estimate the top of bottom-aligned OOFs as bottom. > > We'll incorrectly think that we get fragmented in that case, which will > lead to incorrect height, which will lead to incorrect top offset, > which will lead to incorrect fragmentation. > > This has probably been the cause for a flaky web test, that behaved > even worse in LayoutNG, because in NG we force legacy layout as soon as > fragmentation is involved (so when entering printing, we typically need > to rebuild the entire layout object tree, with no former height to base > the bottom estimate on (which is what saved us when NG is disabled - > ehm, at least most of the time)). > > Bug: 910300 > Change-Id: I8e152f77e9a94bb05e51f02a24be6ef5fe03c6f9 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng > Reviewed-on: https://chromium-review.googlesource.com/c/1355920 > Reviewed-by: Aleks Totic <atotic@chromium.org> > Commit-Queue: Morten Stenshorne <mstensho@chromium.org> > Cr-Commit-Position: refs/heads/master@{#613930} TBR=eae@chromium.org,atotic@chromium.org,mstensho@chromium.org Change-Id: I5949a6a6e0b9e5cfa281b7abcd266ad63f7af85f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 910300 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1363646 Reviewed-by: Roger McFarlane <rogerm@chromium.org> Commit-Queue: Roger McFarlane <rogerm@chromium.org> Cr-Commit-Position: refs/heads/master@{#614025} 05 December 2018, 18:19:34 UTC
d59c66c Nicolas Pena 05 December 2018, 15:33:57 UTC Reland "[EventTiming] Always buffer firstInput" This is a reland of b6e2cb9b364649724a1577b0c842074e12b82f27 Flaky tests are fixed: the assumption that wait is sufficient to expect input events to be processed is false. Original change's description: > [EventTiming] Always buffer firstInput > > Before, we'd buffer the firstInput entry only if it happened before > onload. This CL forces firstInput to always be buffered. This means > EventTiming code is called more in some tests, so the event hardware > timestamp is no longer guaranteed to be nonzero, and a couple of xr > tests require double RAF to avoid competing with the swap promises from > Event Timing. > > Bug: 841224, 843184 > > Change-Id: I942b934c387798c100da4ecfff52affb66ab94e8 > Reviewed-on: https://chromium-review.googlesource.com/c/1355880 > Reviewed-by: Timothy Dresser <tdresser@chromium.org> > Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612703} Bug: 823744, 843184 Change-Id: I5286f3748d35c0c9d5972d301cd5abcf6e453da4 Reviewed-on: https://chromium-review.googlesource.com/c/1358910 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#613973} 05 December 2018, 15:42:04 UTC
2d66758 Philip Jägenstedt 05 December 2018, 15:07:28 UTC Merge remote-tracking branch 'origin/master' into HEAD 05 December 2018, 15:07:28 UTC
9a3a9e1 Luke Bjerring 05 December 2018, 14:55:42 UTC Add performance object 05 December 2018, 15:01:24 UTC
c539843 Luke Bjerring 05 December 2018, 14:54:06 UTC Add idlharness test 05 December 2018, 15:01:24 UTC
6b4c63e Automat af Gränssnitt 05 December 2018, 13:30:37 UTC Add interfaces/event-timing.idl Source: https://github.com/tidoust/reffy-reports/blob/9dd0ab0/whatwg/idl/event-timing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463841803 05 December 2018, 15:01:24 UTC
3f5d8af jugglinmike 05 December 2018, 14:59:26 UTC [wptrunner] Support any Sauce Connect argument (#14356) Implement the command-line argument `--sauce-connect-arg` as a pass-through to the Sauce Connect binary. This gives users more control over the way the binary is configured which is particularly important in combination with the existing `--sauce-connect-binary` argument (since the list of available arguments is subject to change between releases). 05 December 2018, 14:59:26 UTC
54e379b L. David Baron 05 December 2018, 14:07:23 UTC Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/caae48e4e6cf4477e11b6464bccdd5ba679ae31a . (#14375) This contains changes from [bug 1511963](https://bugzilla.mozilla.org/show_bug.cgi?id=1511963) by @mrego, reviewed by @emilio. 05 December 2018, 14:07:23 UTC
290b849 Daniel Vogelheim 05 December 2018, 11:32:22 UTC [Trusted Types] Tests from WICG GitHub ported to WPT WICG GitHub = https://github.com/WICG/trusted-types/tree/master/tests ported Bug: 739170 Change-Id: I56563c16facd7c17d79e7b5625115a0f045618f8 Reviewed-on: https://chromium-review.googlesource.com/c/1209708 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613937} 05 December 2018, 11:40:16 UTC
9f57a56 autofoolip 05 December 2018, 10:55:43 UTC Update interfaces/webxr.idl (#14372) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 05 December 2018, 10:55:43 UTC
e298bbf autofoolip 05 December 2018, 10:53:37 UTC Update interfaces/web-nfc.idl (#14371) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 05 December 2018, 10:53:37 UTC
66004f5 Morten Stenshorne 05 December 2018, 10:40:34 UTC Don't estimate the top of bottom-aligned OOFs as bottom. We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). Bug: 910300 Change-Id: I8e152f77e9a94bb05e51f02a24be6ef5fe03c6f9 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1355920 Reviewed-by: Aleks Totic <atotic@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613930} 05 December 2018, 10:48:15 UTC
f4449f8 jgraham 30 November 2018, 18:42:24 UTC Update wptrunner.py 05 December 2018, 10:26:50 UTC
ff755aa Wes Kocher 29 November 2018, 23:51:21 UTC Make sure --repeat-until-unexpected doesn't loop over zero tests If zero tests are selected to run while --repeat-until-unexpected is specified, wptrunner can get into a fast infinite loop of running nothing until killed by the user. This patch should stop that from happening by breaking the loop after the first iteration of nothing finishes. Differential Revision: https://phabricator.services.mozilla.com/D13204 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504357 gecko-commit: f988af9437f591cc5c7d3917ba370e2edc82d1a6 gecko-integration-branch: central gecko-reviewers: jgraham 05 December 2018, 10:26:50 UTC
30b3f1d Morten Stenshorne 05 December 2018, 06:59:11 UTC [LayoutNG] Honor {min,max}-inline-size when using cached intrinsic size. We store cached min/max intrinsic inline sizes in legacy layout objects. These are normally constrained against {min,max}-inline-size, but not if those values are percentage based, since percentages are obviously not resolvable at the time of calculating intrinsic sizes. In such cases we cannot use the cached values directly. Calculate intrinsic size and apply constraints on our own in such cases. Bug: 900390 Change-Id: I90b8ab590fa97e8ec7929bc1af38cf3824f9ea6b Reviewed-on: https://chromium-review.googlesource.com/c/1360853 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613889} 05 December 2018, 07:07:33 UTC
aaa8f82 Florian Rivoal 05 December 2018, 03:58:14 UTC Merge pull request #14368 from MurakamiShinyu/overflow-wrap [css-text] line-height fix on overflow-wrap-break-word-004 and -005 05 December 2018, 03:58:14 UTC
9ccd954 MurakamiShinyu 05 December 2018, 03:31:07 UTC [css-text] line-height fix on overflow-wrap-break-word-004 and -005 tests - `line-height: 1em` was specified on the `.test {...}` but not on the `.red` and `.fail` blocks. As a result, the line-height of the `.red` and `.fail` blocks depended on the browser, and the red color appeared on Firefox. 05 December 2018, 03:31:07 UTC
c4eb7b7 Jarryd 05 December 2018, 02:13:04 UTC Refactor storage estimate wpt to use async/await. Change-Id: Iec6ddc03ce5a813f219273e4a8a7d5098b3fb936 Reviewed-on: https://chromium-review.googlesource.com/c/1318739 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#613817} 05 December 2018, 02:21:43 UTC
c05265a Kai Ninomiya 05 December 2018, 01:54:09 UTC testharness.md: Remove errant spaces in file paths Removes spaces in /common /subset-tests.js /common/subset-tests-by- key.js 05 December 2018, 02:03:11 UTC
614fd87 MurakamiShinyu 03 December 2018, 07:02:47 UTC [css-text] Update 'line-break' tests ### Fix test file name numbering The problem was that `line-break-normal-*` and `line-break-strict-*` had diffrent numbering for same ranges, e.g. `line-break-normal-021` and `line-break-strict-014` for same iteration marks. It was confusing, so I changed the numbering for 'normal' to be the same as for 'strict'. - line-break-normal-021 → line-break-normal-014 - line-break-normal-022 → line-break-normal-015 - line-break-normal-023a → line-break-normal-016a - line-break-normal-023b → line-break-normal-016b - line-break-normal-024a → line-break-normal-017a - line-break-normal-024b → line-break-normal-017b ### Fix tests for Inseparatable characters The tests for Inseparatable characters `line-break-strict-015` and `line-break-normal-015` (was `line-break-normal-022`) had wrong assertion "does not allow line breaking **before** inseparable characters". This should be "does not allow line breaking **between** inseparable characters". I changed the tests to test line breaking **between** (not **before**) two inseparable characters. ### Fix tests for Centered punctuation marks The tests for Centered punctuation marks `line-break-strict-016a` and `line-break-normal-016a` (was `line-break-normal-023a`) contained tests for EAW=Narrow characters (U+003A, U+003B, U+0021, U+003F) that are excluded in the current 'line-break' spec. ### Fix tests for Postfixes The tests for Postfixes `line-break-strict-017a` and `line-break-normal-017a` (was `line-break-normal-024a`) contained tests for EAW=Narrow characters (U+0025 and U+00A2) that are excluded in the current 'line-break' spec. ### Add tests for Prefixes Added the tests for line breaking after Prefixes `line-break-*-018`. ### Add 'loose' and 'normal' values tests that were missing - line-break-loose-011 .. line-break-loose-017b - line-break-normal-011 .. line-break-normal-013 ### Adjust width of the test block I changed the width of the test block `p.test, p.control {...}` that was `width: 10em` to `width: 10.2em`. This extra (.2em) width is needed to prevent unexpected line breaking caused by some symbol characters wider than 1em. I found this problem with `line-break-loose-018`. The width of U+2116 "№" is slightly wider than 1em and if the block width is 10em the line breaking occurs before that character, and the test always fails. 04 December 2018, 23:16:38 UTC
3960fff MurakamiShinyu 04 December 2018, 15:49:56 UTC [css-text] Some fixes on 'word-break-break-all-*' tests ### word-break-break-all-010 and word-break-break-all-011 - `line-height: 1em` was specified on the `.test {...}` but not on the `.red {...}`. As a result, the line-height of the `.red` block depended on the browser, and the red color appeared on Firefox. ### word-break-break-all-020 Fix erros (typo?) - `div::nth-of-type` → `div:nth-of-type` - `break-word` → `break-all` 04 December 2018, 23:14:56 UTC
164bf82 Stephen McGruer 04 December 2018, 20:12:36 UTC [ScrollTimeline] Begin upstreaming tests to WPT This CL uploads some basic construction tests for ScrollTimeline. Since the Chrome implementation still requires timeRange, it is left in for now (but documented!). Spec: https://wicg.github.io/scroll-animations Bug: 911254 Change-Id: Ia7da845eddcd27ea6e7d3fbaf3a008cbdf6d149a Reviewed-on: https://chromium-review.googlesource.com/c/1354222 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#613666} 04 December 2018, 20:20:41 UTC
1f9bc10 Daniel Vogelheim 04 December 2018, 14:19:21 UTC WorkerGlobalScope::importScripts() modified to accept TrustedTypes Existing implementation made private and renamed importScriptsFromString. New version wraps importScriptsFromString. Service_Worker_Global_Scope::importScripts() signature adjusted to accept TrustedTypes. Bug: 739170 Change-Id: Ifa7d9e9f13f0903ecdf0b4c1553f6039141b9b76 Reviewed-on: https://chromium-review.googlesource.com/c/1144825 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#613538} 04 December 2018, 14:27:30 UTC
4a0a94b Andy Paicu 04 December 2018, 12:32:37 UTC Rework of "inherit the navigation initiator when navigating" Spec: https://w3c.github.io/webappsec-csp/#initialize-document-csp This is a rework and reland of https://chromium-review.googlesource.com/c/chromium/src/+/1314633 The initial patch got reverted because it did not pass the trusty leak build checks. The issue was that holding to the initiator document as a member in FrameLoader was holding said document alive unreasonably long. Instead this rework holds a copy of the initiator's CSP. Bug: 905301, 894228, 836148 Change-Id: Ic12c28d20c53def5d6753449c3c4da7de5242ca2 Reviewed-on: https://chromium-review.googlesource.com/c/1353978 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#613521} 04 December 2018, 12:54:43 UTC
0b2da26 Andy Paicu 04 December 2018, 12:23:51 UTC Fixes to the plugin-types csp checks and added empty directive check Fixed the external/wpt/content-security-policyplugin-types tests as the current ones are actually entirely useless as they pretty much always pass. Discovered and raised crbug.com/911114, also skipping the (now correct) tests that uncovered this issue. Added new test for empty plugin-types directive blocking every plugin. Removed tests in http/tests/security/contentSecurityPolicy that are direct 1-to-1 equivalents of these tests. Spec: https://github.com/w3c/webappsec-csp/pull/374 Bug: 694525 Change-Id: I91a548c6035a82310be077501934a51cf85525a2 Reviewed-on: https://chromium-review.googlesource.com/c/1358457 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613517} 04 December 2018, 12:50:46 UTC
a374387 jgraham 04 December 2018, 11:27:56 UTC Update fennec.py 04 December 2018, 11:50:58 UTC
b7ec9ec James Graham 01 December 2018, 00:35:02 UTC Fixup shutting down fennec Remove the desktop-only shutdown code and ensure that the app isn't running before the tests start, since we can't have multiple copies of the same app running at a time. Depends on D13088 Differential Revision: https://phabricator.services.mozilla.com/D13089 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1510258 gecko-commit: 7d17aa7e056119b29b713caa1bd63d575ad2cc56 gecko-integration-branch: autoland gecko-reviewers: gbrown 04 December 2018, 11:50:58 UTC
6111e21 Ms2ger 30 November 2018, 16:38:11 UTC Fix path argument to wpt lint. 04 December 2018, 11:26:39 UTC
fc6921b Andy Paicu 04 December 2018, 11:03:53 UTC Inherit the self source when we inherit the policy Spec: https://w3c.github.io/webappsec-csp/#initialize-document-csp Bug: 910841 Change-Id: Ic06cf87577c46cfc3a8a2581160c32e22f3956e8 Reviewed-on: https://chromium-review.googlesource.com/c/1357084 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613501} 04 December 2018, 11:11:41 UTC
0dcde64 autofoolip 04 December 2018, 10:51:41 UTC Update interfaces/audio-output.idl (#14069) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/audio-output.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:51:41 UTC
3590884 autofoolip 04 December 2018, 10:50:10 UTC Update interfaces/mediacapture-streams.idl (#13999) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/mediacapture-streams.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:50:10 UTC
e2e3234 autofoolip 04 December 2018, 10:42:43 UTC Update interfaces/payment-method-basic-card.idl (#14070) Source: https://github.com/tidoust/reffy-reports/blob/a74aa91/whatwg/idl/payment-method-basic-card.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/455362278 04 December 2018, 10:42:43 UTC
64a4678 autofoolip 04 December 2018, 10:41:44 UTC Update interfaces/performance-timeline.idl (#14276) Source: https://github.com/tidoust/reffy-reports/blob/6f59720/whatwg/idl/performance-timeline.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/460633569 04 December 2018, 10:41:44 UTC
51acb5a autofoolip 04 December 2018, 10:41:09 UTC Update interfaces/input-events.idl (#14351) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/input-events.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:41:09 UTC
8a1654e autofoolip 04 December 2018, 10:39:38 UTC Update interfaces/credential-management.idl (#14350) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/credential-management.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:39:37 UTC
9093fde Automat af Gränssnitt 04 December 2018, 07:11:18 UTC Update interfaces/DOM-Parsing.idl Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/DOM-Parsing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 09:42:05 UTC
774f67d Gyuyoung Kim 04 December 2018, 05:19:55 UTC [USVString] Add a rough test case for navigator.unregisterProtocolHandler Although r525634 updated the URL type of registerProtocolHandler from DOMString to USVString, it didn't add a test case because it was a bit complex. And also, issue 933668 added the rough test for navigator.registerProtocolHandler. But, it didn't add a test for the navigator.unregisterProtocolHandler. So this CL adds a rough test case for navigator.unregisterProtocolHandler. Bug: 790860 Change-Id: Ib54c058e4c61db59b73486d28fbd3db5bfdd36c7 Reviewed-on: https://chromium-review.googlesource.com/c/1359976 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#613425} 04 December 2018, 05:28:21 UTC
1abcb70 jugglinmike 04 December 2018, 00:24:59 UTC [service-workers] Use asynchronous cleanup (#13164) Previously, many tests un-registered service workers only after all assertions had been satisfied. This meant that failing tests would not un-register workers. In order to account for workers that persisted from previous test failures, the tests included "setup" code to defensively un-register such workers. The `Test#add_cleanup` method was recently extended to support asynchronous "clean up" operations [1]. Use that API to schedule service worker un-registration so that it occurs regardless of the result of each test. [1] https://github.com/web-platform-tests/wpt/pull/8748 04 December 2018, 00:24:59 UTC
ef72a20 Philip Jägenstedt 03 December 2018, 22:49:50 UTC Rename audio-output idlharness test for secure context change (#14337) Needed for https://github.com/web-platform-tests/wpt/pull/14069. 03 December 2018, 22:49:50 UTC
a0aee6e Kevin Ellis 03 December 2018, 19:30:25 UTC Simplify interpolation of 2-D matrix transforms. The decomposition of a transformation matrix into translations, rotation, scale and skew transforms is not unique. In some cases, the generalized 3-D decomposition does not align with the working draft for CSS transforms (https://drafts.csswg.org/css-transforms/). In the special case where the transforms being interpolated are both 2-D, a simplified model provides more restricted set of decomposition transforms with less computational overhead. Bug: 797472 Change-Id: I2b8ba99fe02c2eef878d94f5dfaea55c39652759 Reviewed-on: https://chromium-review.googlesource.com/c/1332253 Commit-Queue: Kevin Ellis <kevers@chromium.org> Commit-Queue: Ian Vollick <vollick@chromium.org> Reviewed-by: Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#613191} 03 December 2018, 19:38:11 UTC
7de8ae3 James Graham 30 November 2018, 18:21:30 UTC Update the docker image 03 December 2018, 18:54:19 UTC
3c36672 James Graham 30 November 2018, 18:21:08 UTC Fetch tags on initial clone This is slow, but means we have the information needed to download the manifest 03 December 2018, 18:54:19 UTC
dedf235 James Graham 30 November 2018, 18:20:03 UTC Move most of start.sh to outside the Docker image This reduces the number of changes that require a rebuild of the docker image. 03 December 2018, 18:54:19 UTC
073eaac Mugdha Lakhani 03 December 2018, 14:41:26 UTC [Background Fetch] Remove records_ from BackgroundFetchRegistration. This had been introduced to simplify access to active fetches, but has the following issues: 1. It makes match() and matchAll() inconsistent with Cache API's match() and matchAll(), which return new independently-consumable response(s) every time they're called. 2. It breaks retries for responses, when downloading from a server that doesn't support resuming of downloads. For details, see https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing The CL also updates the WPT test accordingly. Bug: 875201 Change-Id: I2c33717cbee36f0d707e814506c0bae9b5a4f31f Reviewed-on: https://chromium-review.googlesource.com/c/1355121 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#613079} 03 December 2018, 14:50:54 UTC
b158c0c Automat af Gränssnitt 03 December 2018, 07:10:48 UTC Update interfaces/DOM-Parsing.idl Source: https://github.com/tidoust/reffy-reports/blob/618d45b/whatwg/idl/DOM-Parsing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/462673619 03 December 2018, 13:50:54 UTC
e8ade95 Guido Urdaneta 03 December 2018, 10:58:02 UTC Revert "Enforce active lifetime of XRFrame objects" This reverts commit ff451c7bfc7010d9bea16d7b7036be389afa1db5. Reason for revert: Suspect of causing consistent failure of xr_browser_tests on Win10 Debug (NVIDIA) bot. See https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Debug%20%28NVIDIA%29 First failure: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Debug%20%28NVIDIA%29/10962 Original change's description: > Enforce active lifetime of XRFrame objects > > Deactivates XRFrame objects once the relevant callback returns, which > causes future calls to the object methods to throw an exception. > > Bug: 906842 > Change-Id: I192453f9f23b1b4d9a404daca352ab80a5393753 > Reviewed-on: https://chromium-review.googlesource.com/c/1343065 > Commit-Queue: Brandon Jones <bajones@chromium.org> > Reviewed-by: Klaus Weidner <klausw@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612887} TBR=bajones@chromium.org,klausw@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 906842 Change-Id: I26eb3477ea875362a5f1e6fd0b67bbe4a3c2c4a5 Reviewed-on: https://chromium-review.googlesource.com/c/1356945 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#613039} 03 December 2018, 11:06:30 UTC
15ec1e3 Morten Stenshorne 03 December 2018, 10:14:13 UTC Consistently round table row heights. Do in LogicalHeightForRow() as in CalcRowLogicalHeight() - i.e. round instead of floor, to convert from LayoutUnit to int. We calculated the pagination strut incorrectly for the line that followed, because it was based on the floored LayoutUnit height of the preceding table row. Then, later on, it got adjusted (rounded from LayoutUnit), and the balancing code got confused, because the line had a pagination strut, but didn't appear to be exactly at the start of a column (there should be no strut in such a case). Bug: 908247 Change-Id: I11fa5430b9ff6e83b20dc25ce1d945e54b80f6ea Reviewed-on: https://chromium-review.googlesource.com/c/1356551 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#613033} 03 December 2018, 10:23:00 UTC
5377da8 autofoolip 03 December 2018, 10:18:08 UTC Update interfaces/input-events.idl (#13998) Source: https://github.com/tidoust/reffy-reports/blob/618d45b/whatwg/idl/input-events.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/462673619 03 December 2018, 10:18:08 UTC
54b405c Wes Kocher 28 November 2018, 01:08:31 UTC Only __getitem__() in dicts that include the desired key to avoid printing tracebacks Differential Revision: https://phabricator.services.mozilla.com/D12998 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1506132 gecko-commit: ffe333026cf81c22cabfbf936f6b9550103e924d gecko-integration-branch: central gecko-reviewers: jgraham 02 December 2018, 20:34:49 UTC
de9a09a James Graham 01 December 2018, 00:34:49 UTC Enable wpt android reftests on try/m-c Depends on D13089 Differential Revision: https://phabricator.services.mozilla.com/D13090 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1509983 gecko-commit: a72c668be4352bd19d650019384ba44de24cc795 gecko-integration-branch: autoland gecko-reviewers: gbrown, ato 01 December 2018, 12:42:50 UTC
92a317b James Graham 01 December 2018, 00:34:34 UTC Remove custom FirefoxRunner subclass This was only being used to set prefs and most prefs are either already set in testing/profiles/[common|unittest|web-platform-tests].js or can be set there so they apply to desktop too. Differential Revision: https://phabricator.services.mozilla.com/D13088 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1510254 gecko-commit: ed149f9cf50a61f1a6f90f3163d89d809414d632 gecko-integration-branch: autoland gecko-reviewers: gbrown, KWierso 01 December 2018, 11:15:52 UTC
081cae2 autofoolip 01 December 2018, 08:32:54 UTC Update interfaces/web-nfc.idl (#14325) Source: https://github.com/tidoust/reffy-reports/blob/c609c4b/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/462099771 01 December 2018, 08:32:54 UTC
9d21471 Brandon Jones 01 December 2018, 01:20:09 UTC Enforce active lifetime of XRFrame objects Deactivates XRFrame objects once the relevant callback returns, which causes future calls to the object methods to throw an exception. Bug: 906842 Change-Id: I192453f9f23b1b4d9a404daca352ab80a5393753 Reviewed-on: https://chromium-review.googlesource.com/c/1343065 Commit-Queue: Brandon Jones <bajones@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#612887} 01 December 2018, 01:28:08 UTC
d506921 MurakamiShinyu 30 November 2018, 05:29:35 UTC [css-text] Rename 'white-space-collapsing-*' test files 30 November 2018, 22:21:42 UTC
17482d3 MurakamiShinyu 30 November 2018, 05:22:59 UTC [css-text] Rename 'white-space-collapsing-*' ref files 30 November 2018, 22:21:42 UTC
0d05dbb MurakamiShinyu 30 November 2018, 03:44:24 UTC [css-text] Rename 'white-space-collapsing' on ref files also fix the "trim-inner" test ref (the test was fixed in my previous commit) 30 November 2018, 22:21:42 UTC
5ab7442 MurakamiShinyu 30 November 2018, 02:58:04 UTC [css-text] Move 'white-space-collapsing' tests to Level 4 with renaming 30 November 2018, 22:21:42 UTC
eeb0f94 Sebastien Seguin-Gagnon 30 November 2018, 21:30:46 UTC Revert "[EventTiming] Always buffer firstInput" This reverts commit b6e2cb9b364649724a1577b0c842074e12b82f27. Reason for revert: Causing WebKitLayout tests failure on linux: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/76109 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/76108 Original change's description: > [EventTiming] Always buffer firstInput > > Before, we'd buffer the firstInput entry only if it happened before > onload. This CL forces firstInput to always be buffered. This means > EventTiming code is called more in some tests, so the event hardware > timestamp is no longer guaranteed to be nonzero, and a couple of xr > tests require double RAF to avoid competing with the swap promises from > Event Timing. > > Bug: 841224, 843184 > > Change-Id: I942b934c387798c100da4ecfff52affb66ab94e8 > Reviewed-on: https://chromium-review.googlesource.com/c/1355880 > Reviewed-by: Timothy Dresser <tdresser@chromium.org> > Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612703} TBR=tdresser@chromium.org,npm@chromium.org Change-Id: I4b2456f4b9f44798b3157bea960d84f72a50a8bb No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 841224, 843184 Reviewed-on: https://chromium-review.googlesource.com/c/1357404 Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org> Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#612790} 30 November 2018, 21:38:17 UTC
aec5b0d Darshan Kadu 30 November 2018, 20:21:11 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=188189 (#14314) * added perform-microtask-checkpoint-before-construction test 30 November 2018, 20:21:11 UTC
5db2938 Nicolas Pena 30 November 2018, 18:29:30 UTC [EventTiming] Always buffer firstInput Before, we'd buffer the firstInput entry only if it happened before onload. This CL forces firstInput to always be buffered. This means EventTiming code is called more in some tests, so the event hardware timestamp is no longer guaranteed to be nonzero, and a couple of xr tests require double RAF to avoid competing with the swap promises from Event Timing. Bug: 841224, 843184 Change-Id: I942b934c387798c100da4ecfff52affb66ab94e8 Reviewed-on: https://chromium-review.googlesource.com/c/1355880 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#612703} 30 November 2018, 18:37:45 UTC
c2ab83d Emilio Cobos Álvarez 30 November 2018, 15:29:30 UTC Implement page-break-{before,after} as legacy shorthands for {before,after}. This is all the style-system work needed for this. This implements the concept of legacy shorthands, teaches tests to understand it, and adds a few more tests for these properties in particular. The WPT even caught a few WebKit / Blink bugs: https://bugs.chromium.org/p/chromium/issues/detail?id=906336 https://bugs.webkit.org/show_bug.cgi?id=191803 This doesn't change the layout behavior for page-break-before: always, since it'd stop breaking in multicol and such. Similarly, break-before / break-after: column and page still behave the same, I'll file followups for those given comment 22. Differential Revision: https://phabricator.services.mozilla.com/D12211 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=775618 gecko-commit: b4c0c0fecdba68979d41609d3978fe596078d0cd gecko-integration-branch: central gecko-reviewers: heycam 30 November 2018, 18:27:48 UTC
4607d19 autofoolip 30 November 2018, 12:10:03 UTC Update interfaces/screen-capture.idl (#14308) Source: https://github.com/tidoust/reffy-reports/blob/1a7aa08/whatwg/idl/screen-capture.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/461650522 30 November 2018, 12:10:03 UTC
cf61291 Chris Lilley 30 November 2018, 09:51:58 UTC Merge pull request #14310 from web-platform-tests/convert_svg11 Convert SVG 1.1 marker tests to reftests. 30 November 2018, 09:51:58 UTC
d52879f Nikos Andronikos 18 October 2016, 05:29:49 UTC Convert SVG 1.1 marker tests to reftests. Correct result of marker tests because SVG 2 changes marker overflow auto to be visible Update to resolve anti-aliasing differences. Also addressed some other minor comments made by AmeliaBR. 30 November 2018, 09:21:56 UTC
efcbb44 Jan Varga 30 November 2018, 05:40:39 UTC Part 14: Enhance clearStoragesForPrincipal() to support clearing of storages for specific quota client See also bug 1402254, original patch by baku. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1286798 gecko-commit: 20606f9de28fd7dff30f30b3862b2bdc68df85b3 gecko-integration-branch: central gecko-reviewers: asuth 30 November 2018, 07:07:46 UTC
38eec61 Jeffrey Yasskin 30 November 2018, 02:24:01 UTC Test navigation when a SW replies with a fetch from a different URL (#14288) The resulting document's location should be the originally requested URL. See also https://github.com/whatwg/html/pull/4205 30 November 2018, 02:24:01 UTC
026c2b6 Andreas Butler 30 November 2018, 00:38:29 UTC [IndexedDB]: Implement explicit commit() in renderer Implementing an explicit commit function for the IndexedDB Transaction API. The addition of this API allows developers to preempt IndexedDB's autocommit functionality by sending their own explicit commit signal. Explainer: https://andreas-butler.github.io/idb-transaction-commit/EXPLAINER Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=898257 Change-Id: I5e8bdc697052139d014757408d9a7f2b6367655b Reviewed-on: https://chromium-review.googlesource.com/c/1300055 Commit-Queue: Andreas Butler <andreasbutler@google.com> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#612474} 30 November 2018, 00:49:53 UTC
3035063 Hwanseung Lee 30 November 2018, 00:38:19 UTC [GeometryInterface] add scaleNonUniform method in DOMMatrixReadOnly DOMMatrix should be alias to SVGMatrix. (It was not implement in blink yet) SVGMatrix have scaleNonUniform() function. but DOMMatrix was not. there are some website which is used SVGMatrix.scaleNonUniform(). it would be possible brake some website when DOMMatrix be alias to SVGMatrix. Intent to implement and ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/BJJKDby5p7w Bug: 905921 Change-Id: Ic09b8d6e46d0aa822b766bd6cfbc5ce7c2164849 Reviewed-on: https://chromium-review.googlesource.com/c/1341279 Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Reviewed-by: Jinho Bang <jinho.bang@samsung.com> Cr-Commit-Position: refs/heads/master@{#612473} 30 November 2018, 00:46:12 UTC
00942a1 Emilio Cobos Álvarez 29 November 2018, 17:05:04 UTC Prevent exponential blowup of custom properties. Put a hard cap on the value length instead of counting substitutions, because it works best, see the comment. Differential Revision: https://phabricator.services.mozilla.com/D13352 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1510862 gecko-commit: e593d06bcd929ab543824921434def8c6e4c6c5b gecko-integration-branch: central gecko-reviewers: jwatt 29 November 2018, 23:24:43 UTC
d67fec6 Navid Zolghadr 29 November 2018, 17:12:05 UTC Remove trailing space and add a "the" 29 November 2018, 22:53:29 UTC
07e35f3 Navid Zolghadr 28 November 2018, 21:16:13 UTC Add actions builder API documentation Add actions builder API documentation plus some examples 29 November 2018, 22:53:29 UTC
3afcfd2 Andrew Comminos 29 November 2018, 22:38:22 UTC Add web platform test for verifying first byte timing of responseStart Verfies that the UA measures the time before the end of header parsing in responseStart by simulating a delay after writing the status line and flushing to the client. Chrome fails this test for now, but Firefox passes. Bug: 568024 Change-Id: I61569c6a5b0d8ea2f3a06cb37a3d1ed36c06d40f Reviewed-on: https://chromium-review.googlesource.com/c/1354645 Commit-Queue: Andrew Comminos <acomminos@fb.com> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#612412} 29 November 2018, 22:45:49 UTC
6911a29 qiuzhong 29 November 2018, 22:27:31 UTC Remove timeout from async_test for argument form. (#14273) There're cases that the timeout is passing to async_test in the tests. They should be removed as well. Related: #11120 29 November 2018, 22:27:31 UTC
f1be712 Mason Freed 29 November 2018, 19:57:41 UTC Adding more WPT tests for backdrop-filter This set includes a few more known issues, and changes the definition of opacity to match our more recent proposal. Under that proposal, the opacity of the backdrop-filter element applies to the filtered backdrop image as well. Bug: 497522 Change-Id: I2fa0bbb710b7a4ba5592c9a4b9ea5ecaaf5b9ddf Reviewed-on: https://chromium-review.googlesource.com/c/1354347 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#612325} 29 November 2018, 21:35:35 UTC
25f3222 youennf 29 November 2018, 20:07:36 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=191986 (#14286) 29 November 2018, 20:07:36 UTC
02621fd Robert Ma 28 November 2018, 22:55:57 UTC Attempt to monitor memory from userspace It is suspected that Taskcluster jobs sometimes fail due to OOM. It is hard to know what exactly happens if the kernel OOM killer kicks in. This change attempts to use a user-space solution: earlyoom. There are two benefits of earlyoom: 1. Logging: we can log the memory usage periodically and the actions taken by earlyoom when the system is low on memory. 2. Recovery: we can teach earlyoom to prefer to kill browser processes and avoid python processes (wpt) so that the runner has a chance to recover (marking the test as CRASH and carrying on). 29 November 2018, 19:25:57 UTC
265b7a1 jugglinmike 29 November 2018, 19:11:09 UTC [permissions] Add tests for "Set Permission" (#12118) https://w3c.github.io/permissions/#automation 29 November 2018, 19:11:09 UTC
a2e7e01 Nicolas Pena 29 November 2018, 16:01:52 UTC Move EventTiming tests to WPT Try 3 This CL moves the tests in http/tests/event-timing to external/wpt/event-timing. The slow image is change from php based to python based. The click is now handled by test driver. and setTimeout is replaced with step_timeout. Bug: 841224, 908187, 907948, 907949 Change-Id: Ia6359878666cfb96645aa3b7cd7736ce9df97683 Reviewed-on: https://chromium-review.googlesource.com/c/1352617 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#612214} 29 November 2018, 16:10:41 UTC
b28b033 Chris Lilley 29 November 2018, 15:24:22 UTC Merge pull request #14111 from ewilligers/svg-text-parsing SVG Text Parsing 29 November 2018, 15:24:22 UTC
af06307 Mike Conley 26 November 2018, 23:30:47 UTC Split out prefetch test from fetch-destination.https.html, and disable for Firefox. Differential Revision: https://phabricator.services.mozilla.com/D12944 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503852 gecko-commit: d534baf412772ee14e0d89f651267cb4dc2a3f6c gecko-integration-branch: autoland gecko-reviewers: jgraham 29 November 2018, 14:52:55 UTC
fab7e0b Ting-Yu Lin 19 November 2018, 22:29:20 UTC Do not span column-span:all element across all columns if it's under different block formatting context. multicol-span-all-004-ref.html is the same as multicol-span-all-004.html except for the "column-span" value in h3. Differential Revision: https://phabricator.services.mozilla.com/D12192 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1506163 gecko-commit: a5e00e5b4635a19e9fb4ed3566565504338384c6 gecko-integration-branch: mozilla-inbound gecko-reviewers: bz 29 November 2018, 14:43:16 UTC
04d65b3 John Chen 28 November 2018, 17:39:49 UTC Remove browserName from default Chrome capabilities The configuration for Chrome currently sends 'browserName' capability to ChromeDriver by default. This is unnecessary, and causes errors in several test cases in webdriver/tests/new_session, whenever a test case wants to set a different browserName. 29 November 2018, 10:35:05 UTC
9118ed3 autofoolip 29 November 2018, 09:16:25 UTC Update interfaces/payment-request.idl (#14296) Source: https://github.com/tidoust/reffy-reports/blob/a232594/whatwg/idl/payment-request.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/461143420 29 November 2018, 09:16:25 UTC
be0d224 autofoolip 29 November 2018, 09:15:54 UTC Update interfaces/webxr.idl (#14013) Source: https://github.com/tidoust/reffy-reports/blob/a232594/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/461143420 29 November 2018, 09:15:54 UTC
32886e6 Ryosuke Niwa 29 November 2018, 09:01:32 UTC Move back resources/ustom-elements-helpers.js into custom-elements/resources/custom-elements-helpers.js after darsh7807 (#14295) This file has no business being in the top-level resources directory. 29 November 2018, 09:01:32 UTC
38ba051 Mounir Lamouri 28 November 2018, 23:07:24 UTC Media Capabilities: implement response side of Encrypted Media. This is adding an DecodingInfo class that carries key system access information back and create a MediaKeySystemAccess. This implementation in //media/blink is a stub that is meant to only pass WPT tests at the moment. Bug: 907909 Change-Id: I3bac0087ca3051defb8b47d10fffdb6052814ae9 Reviewed-on: https://chromium-review.googlesource.com/c/1348733 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by: Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#611917} 28 November 2018, 23:16:11 UTC
7268cc5 Mounir Lamouri 28 November 2018, 21:28:39 UTC Media Capabilities: implement Blink shell of encrypted media support. This is adding the interface changes, the code checking for corectedness, does type conversion and checks for the edge cases mentioned in spec. This is also adding WPT. Bug: 907909 Change-Id: Ieebe5b25202a403e50a09576ac283690c0f0ba55 Reviewed-on: https://chromium-review.googlesource.com/c/1348972 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#611871} 28 November 2018, 21:37:06 UTC
d021d84 Fredrik Söderquist 28 November 2018, 20:15:08 UTC Disabled (empty) SVG shapes cannot be hit Disabled SVG shapes [1][2][3] should not be possible to hit since they are considered "not rendered". [1] https://svgwg.org/svg2-draft/shapes.html#RectElement [2] https://svgwg.org/svg2-draft/shapes.html#CircleElement [3] https://svgwg.org/svg2-draft/shapes.html#EllipseElement Bug: 896641 Change-Id: I5fe530722a4d60ecd416cd68f06a7555bb6a520f Reviewed-on: https://chromium-review.googlesource.com/c/1353983 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#611840} 28 November 2018, 20:23:54 UTC
back to top