3f4077205ff537d67be27ed7a056de4afc332a6d: Bug 1465045 [wpt PR 11223] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 30 May 2018 12:40:37 +0000 - rev 424239
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1465045 [wpt PR 11223] - Update wpt metadata, a=testonly wpt-pr: 11223 wpt-type: metadata
9dbde9dbe6ab45ee886ec24678140123829b7a96: Bug 1465045 [wpt PR 11223] - Make multiple-workers tests fail if (Shared)Worker is not defined, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 25 Jun 2018 21:40:58 +0000 - rev 424238
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1465045 [wpt PR 11223] - Make multiple-workers tests fail if (Shared)Worker is not defined, a=testonly Automatic update from web-platform-testsMake multiple-workers tests fail if (Shared)Worker is not defined Fixes #11222. Part of #11269. -- wpt-commits: 4f7d09666f738d1db19ba49721b2db4330bf4e82 wpt-pr: 11223
df584a35ba764e1c26f400f095fd8e9a8e33499f: Bug 1459354 [wpt PR 10857] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 Jun 2018 20:57:38 +0000 - rev 424237
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1459354 [wpt PR 10857] - Update wpt metadata, a=testonly wpt-pr: 10857 wpt-type: metadata
19214723eb555dd49bda82a731cbcc6cae28f661: Bug 1459354 [wpt PR 10857] - WaveShaper must output non-zero values even if input is silent, a=testonly
Raymond Toy <rtoy@chromium.org> - Mon, 25 Jun 2018 21:39:35 +0000 - rev 424236
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1459354 [wpt PR 10857] - WaveShaper must output non-zero values even if input is silent, a=testonly Automatic update from web-platform-testsWaveShaper must output non-zero values even if input is silent If the curve for the WaveShaperNode is such that a zero input produces a non-zero output, the WaveShaperNode needs to output that value even if the input is silent (or disconnected). Do this by setting the tail time of the processor to 0 or infinity depending on whether the curve specifies an output value of zero or not, respectively. Bug: 807301 Test: WaveShaper/silent-inputs.html Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b Reviewed-on: https://chromium-review.googlesource.com/896266 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#564186} -- wpt-commits: 5007510675fa679ff60a44a9d10ae33903fa275c wpt-pr: 10857
70884c5b945b3601e5b5b6ea47987d428eef55cb: Bug 1466442 [wpt PR 11319] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186254, a=testonly
youennf <youennf@users.noreply.github.com> - Mon, 25 Jun 2018 21:38:15 +0000 - rev 424235
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466442 [wpt PR 11319] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186254, a=testonly Automatic update from web-platform-testsMerge pull request #11319 from youennf/wpt-export-for-webkit-186254 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186254 -- wpt-commits: 1e64b416a81befaae0b180c1033651fda12e6777 wpt-pr: 11319
3aa91112b82e5dcc4fab7e92a38920dcfd947dcd: Bug 1466566 [wpt PR 11327] - Core-AAM: Add tests for blockquote, caption, and paragraph roles, a=testonly
joanmarie <jdiggs@igalia.com> - Mon, 25 Jun 2018 21:36:58 +0000 - rev 424234
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466566 [wpt PR 11327] - Core-AAM: Add tests for blockquote, caption, and paragraph roles, a=testonly Automatic update from web-platform-testsCore-AAM: Add tests for blockquote, caption, and paragraph roles (#11327) -- wpt-commits: e276a8bb54a4ea45b2c3268234e1f99fe3c977f9 wpt-pr: 11327
1d072cab53cce4e9293d007baa74911ee2897e8b: Bug 1466557 [wpt PR 8584] - Clarify expectations and disable failing cookie tests, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Mon, 25 Jun 2018 21:35:41 +0000 - rev 424233
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466557 [wpt PR 8584] - Clarify expectations and disable failing cookie tests, a=testonly Automatic update from web-platform-testsClarify expectations for failing cookie tests (#8584) These clean ups are split out from https://crrev.com/c/788217: - Defining the assert failure messages Change-Id: I74ba2bb70e907a28292301046a7433480ab669d8 -- wpt-commits: 64f8dcf90b637440e557fc9bd6b11316a3129c18 wpt-pr: 8584
23537fd3d4d43adf878e4fe10f2c521e6f9f193a: Bug 1466463 [wpt PR 11322] - Update git documentation, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Mon, 25 Jun 2018 21:34:24 +0000 - rev 424232
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466463 [wpt PR 11322] - Update git documentation, a=testonly Automatic update from web-platform-testsUpdate git documentation (#11322) Remove parts that are no longer relevant (we only have one repo now, we no longer use submodules...), and update graphics. Related to #5301 -- wpt-commits: 3b8c1c4810dfb47c16016e324321ddeba97c4a15 wpt-pr: 11322
b2f2b67ec7ee492d4cdaae67ecaaf32611bc7218: Bug 1466273 [wpt PR 11311] - Update assert, help, reviewer and titles to match current ouput of w3c/woff2-tests, a=testonly
Frédéric Wang <fwang@igalia.com> - Mon, 25 Jun 2018 21:32:51 +0000 - rev 424231
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466273 [wpt PR 11311] - Update assert, help, reviewer and titles to match current ouput of w3c/woff2-tests, a=testonly Automatic update from web-platform-testsRemove extra space from '<link rel="reviewer" title="Chris Lilley"' The following command was applied: sed -i 's/<link rel/<link rel/' *.xht This matches the current spacing from https://github.com/w3c/woff2-tests -- Update assert, help, titles to match current ouput of w3c/woff2-tests -- wpt-commits: cfae5d21db808c41357e4e61aa83ea375fe99809, 018f0589197bfbf9e3adeb0952b097bba94710c2 wpt-pr: 11311
83e0ddd30830d45155d0554da3bfffa36b918adb: Bug 1466108 [wpt PR 11297] - Remove unused environment import., a=testonly
Ms2ger <Ms2ger@gmail.com> - Mon, 25 Jun 2018 21:31:36 +0000 - rev 424230
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466108 [wpt PR 11297] - Remove unused environment import., a=testonly Automatic update from web-platform-testsRemove unused environment import. -- wpt-commits: c6676495777e12161aee364ab8932cee2a867c95 wpt-pr: 11297
1135f049cd2baf8cb1a62799f249859c6b1982b5: Bug 1464931 [wpt PR 11208] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 29 May 2018 03:51:13 +0000 - rev 424229
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1464931 [wpt PR 11208] - Update wpt metadata, a=testonly wpt-pr: 11208 wpt-type: metadata
fc9ddda80375cea7d356d55e6949028a178e9230: Bug 1464931 [wpt PR 11208] - Do not allow the empty string as a facingMode constraint value for MediaStreams., a=testonly
Guido Urdaneta <guidou@chromium.org> - Mon, 25 Jun 2018 21:30:14 +0000 - rev 424228
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1464931 [wpt PR 11208] - Do not allow the empty string as a facingMode constraint value for MediaStreams., a=testonly Automatic update from web-platform-testsDo not allow the empty string as a facingMode constraint value for MediaStreams. The empty string is an invalid facingMode value that was being interpreted to be equivalent to the internal facing-mode value of NONE. Bug: 814309 Change-Id: I260fbc41fd17a8bdcd1ca63baffe3bed14f3c4ab Reviewed-on: https://chromium-review.googlesource.com/1072471 Reviewed-by: Harald Alvestrand <hta@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#564046} -- wpt-commits: 2d0250896ebe871e950ac6c4c8acfa3ec7d5c72d wpt-pr: 11208
de4f279eb9f7c6c700c917cca180c6144ecea31a: Bug 1465780 [wpt PR 11273] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 01 Jun 2018 17:09:33 +0000 - rev 424227
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1465780 [wpt PR 11273] - Update wpt metadata, a=testonly wpt-pr: 11273 wpt-type: metadata
0e73052adb50787f209b17bf5242b8b33d322c01: Bug 1465780 [wpt PR 11273] - [css-paint-api] Fail a reftest early if CSS.registerProperty is not s…, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 25 Jun 2018 21:28:46 +0000 - rev 424226
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1465780 [wpt PR 11273] - [css-paint-api] Fail a reftest early if CSS.registerProperty is not s…, a=testonly Automatic update from web-platform-tests[css-paint-api] Fail a reftest early if CSS.registerProperty is not supported Part of #11269. Also fix remaining instances of CSS.registerProperty -- wpt-commits: 0b66b59f9d2684e6ac3dc7dd7b5d633c515f22ac wpt-pr: 11273
d27806bd46a7f2a16cec0f107f70858b3201b12d: Bug 1466064 [wpt PR 11290] - Add a WPT for Service-Worker header, a=testonly
Kenichi Ishibashi <bashi@chromium.org> - Mon, 25 Jun 2018 21:27:19 +0000 - rev 424225
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466064 [wpt PR 11290] - Add a WPT for Service-Worker header, a=testonly Automatic update from web-platform-testsAdd a WPT for Service-Worker header The spec requires that an HTTP request to fetch a service worker script has 'Service-Worker: script' header[1]. [1] https://w3c.github.io/ServiceWorker/#update-algorithm Bug: 848265 Change-Id: I76c836fcf43d287bcac910c3655e5b127ad8555c Reviewed-on: https://chromium-review.googlesource.com/1082253 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#564023} -- wpt-commits: 6ed8b9045489f5d5fd00da465c3cd1df443787be wpt-pr: 11290
ac7e7035d5b1872c9284e96f4a5052c19c01d6eb: Bug 1466460 [wpt PR 11321] - cc Update messages.json, a=testonly
Michael[tm] Smith <mike@w3.org> - Mon, 25 Jun 2018 21:26:01 +0000 - rev 424224
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466460 [wpt PR 11321] - cc Update messages.json, a=testonly Automatic update from web-platform-testscc Update messages.json -- wpt-commits: 5b2eb3f4001e57feb01a7305d4b1f6c42b8fbba7 wpt-pr: 11321
dba098bdbcc1bea0a3af28707d081ffd9dd865d8: Bug 1466206 [wpt PR 11306] - Add filtering support to ManifestLoader., a=testonly
Ms2ger <Ms2ger@gmail.com> - Mon, 25 Jun 2018 21:24:46 +0000 - rev 424223
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466206 [wpt PR 11306] - Add filtering support to ManifestLoader., a=testonly Automatic update from web-platform-testsAdd filtering support to ManifestLoader. In some use cases, the overhead of creating data structures for all tests in the manifest, and then filtering them, is too big. This change allows users to filter tests when initially creating the manifest. -- wpt-commits: f1815a9219ee5ec7fe27ef7a5cfb3fa00b8485c7 wpt-pr: 11306
b5466bfc47246f1f3a779fa38393f949256b91dd: Bug 1464182 [wpt PR 11146] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 24 May 2018 23:24:41 +0000 - rev 424222
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1464182 [wpt PR 11146] - Update wpt metadata, a=testonly wpt-pr: 11146 wpt-type: metadata
d93ccdd537a6636102ea89d4e14d9c9d1688d604: Bug 1464182 [wpt PR 11146] - PaymentHandler: Fix a crash when creating event object with empty data, a=testonly
Jinho Bang <jinho.bang@samsung.com> - Mon, 25 Jun 2018 21:22:21 +0000 - rev 424221
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1464182 [wpt PR 11146] - PaymentHandler: Fix a crash when creating event object with empty data, a=testonly Automatic update from web-platform-testsPaymentHandler: Fix a crash when creating event object with empty data The following codes cause crashes in current implementation. - new CanMakePaymentEvent("canmakepaymentevent", {}); - new PaymentRequestEvent("paymentrequestevent", {}); This patch fixes the problem and fixes/adds WPT tests. Bug: none Change-Id: I95375f1148d69a17075d393990e3726ad2bf1cf3 Reviewed-on: https://chromium-review.googlesource.com/1070957 Commit-Queue: Jinho Bang <jinho.bang@samsung.com> Reviewed-by: Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#563903} -- wpt-commits: 1dc612f2ed6a6bec861a90ad9bfa9a4336165dcd wpt-pr: 11146
f585ab570e26816c9d85de860f39bfd9557b5be3: Bug 1466260 [wpt PR 11309] - Revert "Cleanup plugin element frames when the layout tree is detached", a=testonly
Ehsan Karamad <ekaramad@chromium.org> - Mon, 25 Jun 2018 21:21:04 +0000 - rev 424220
Push 34201 by shindli@mozilla.com at Thu, 28 Jun 2018 21:54:04 +0000
Bug 1466260 [wpt PR 11309] - Revert "Cleanup plugin element frames when the layout tree is detached", a=testonly Automatic update from web-platform-testsRevert "Cleanup plugin element frames when the layout tree is detached" This reverts commit 596e6b3281a8cc2c4b646553e4cde169a29a1d1d. Reason for revert: DetachLayoutTree could be called at inopportune times such as style recalc or during layout. This caused several crashes. Original change's description: > Cleanup plugin element frames when the layout tree is detached > > Unlike frames, plugin elements (<embed> and <object>) are updated > when their layout tree is rebuilt. However, due to an oversight, > <embed> or <object> elements displaying subframes would only have > the associated content view (FrameView) torn down, leaving a > dangling content frame. > > This led to some interesting side effects: > - When transitioning from a local frame to a plugin, the content > frame would remain live, with JS still happily running. > - When transitioning from a remote frame to a plugin, > - When navigating a remote frame from one URL to another, the > element would stop updating since the FrameView would be torn > down but a new one would never be created. Note that this was > not (as much of) a problem for local frames, since local frames > re-create the LocalFrameView on every navigation. > With this CL, if a plugin element has an associated content frame, > use that to clean up the state associated with the element when the > layout tree is detached. This can cause the browser context to be > re-created: this matches the behavior of Edge and Firefox. > > Note that there is still one edge case where Blink behaves oddly: > if the navigation fails and should display fallback content, the > content frame still remains attached. This will be addressed in > followups. > > Link to whatwg issue: https://github.com/whatwg/html/issues/3576 > > Bug: 776510, 781880 > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng > Change-Id: Id18605fbe602ea6c0076c1d579345cdcf28cc984 > Reviewed-on: https://chromium-review.googlesource.com/996314 > Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Cr-Commit-Position: refs/heads/master@{#561768} TBR=dcheng@chromium.org,creis@chromium.org,alexmos@chromium.org,ekaramad@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 776510, 781880, 847216, 846708 Change-Id: I762631b92463352bea9bf3102d90a13b72776786 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/1083500 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Ehsan Karamad <ekaramad@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#563902} -- wpt-commits: 69a48d90cac792566f14d734d2bae4feda462829 wpt-pr: 11309
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip