4ff137e10c3f9aae0e94c57268db34b983e81121: Bug 1466602 [wpt PR 11330] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 Jun 2018 07:42:13 +0000 - rev 424091
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466602 [wpt PR 11330] - Update wpt metadata, a=testonly wpt-pr: 11330 wpt-type: metadata
2e94891d59b8c7abac246d45191ed79755ad1afb: Bug 1466602 [wpt PR 11330] - [LayoutNG] Need to know when establishing a new FC during min/max calculation., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Mon, 25 Jun 2018 21:53:14 +0000 - rev 424090
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466602 [wpt PR 11330] - [LayoutNG] Need to know when establishing a new FC during min/max calculation., a=testonly Automatic update from web-platform-tests[LayoutNG] Need to know when establishing a new FC during min/max calculation. When we have to lay out an object to determine its min/max inline size, and the node establishes a new formatting context, we need to create a constraint space that reflects this. The block size of the float needs to be included in the block size of its container, because this block size will be the min/max preferred inline size of the container of that container, if the writing modes are orthogonal. Avoid some duplicate code for creating the constraint space builder. The second builder, the one that redoes layout with infinite available space now gets SetFloatsBfcOffset() called, which was previously missing, but that must have been an oversight. This fixes the recently introduced regression with fast/multicol/vertical-rl/column-rules.html and also another test. Wrote a new test that tests exactly what I wanted to fix as well. Bug: 847807 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I7b28a0ef8061fc3089deb488ad0a78b81776295d Reviewed-on: https://chromium-review.googlesource.com/1084989 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#564438} -- wpt-commits: aa5ec97282685cba4a2ae34165ddb5043c251e39 wpt-pr: 11330
11108df0fae4d0f5c5d794fcf76277318058a9b4: Bug 1466770 [wpt PR 11341] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 Jun 2018 23:46:36 +0000 - rev 424089
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466770 [wpt PR 11341] - Update wpt metadata, a=testonly wpt-pr: 11341 wpt-type: metadata
efd28be672f5976f64a9f9e99a2feb0fc1bff7a7: Bug 1466770 [wpt PR 11341] - HTML: Fix sandbox-disallow-same-origin.html to expect SecurityError, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 25 Jun 2018 21:51:52 +0000 - rev 424088
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466770 [wpt PR 11341] - HTML: Fix sandbox-disallow-same-origin.html to expect SecurityError, a=testonly Automatic update from web-platform-testsHTML: Fix sandbox-disallow-same-origin.html to expect SecurityError Part of #11269. -- wpt-commits: e4fd758fb3ed204ec4234eb678323273a99eb685 wpt-pr: 11341
e957fe1981f27483f16c7c7db99ea20fc3079b57: Bug 1465437 [wpt PR 11249] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 31 May 2018 17:59:05 +0000 - rev 424087
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1465437 [wpt PR 11249] - Update wpt metadata, a=testonly wpt-pr: 11249 wpt-type: metadata
8119ee3bcb261511106e18c1fbc9509e33d15918: Bug 1465437 [wpt PR 11249] - Fetch: port blocking change (427, 548), a=testonly
Anne van Kesteren <annevk@annevk.nl> - Mon, 25 Jun 2018 21:50:27 +0000 - rev 424086
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1465437 [wpt PR 11249] - Fetch: port blocking change (427, 548), a=testonly Automatic update from web-platform-testsFetch: port blocking change (427, 548, 6697) See https://github.com/whatwg/fetch/pull/738. -- wpt-commits: 2b0cd6155aa269d3ee6e940edb1b2f5c1d5ae1ed wpt-pr: 11249
8c83448ff8309053d0f014d8fb6a193b83a99ed8: Bug 1466366 [wpt PR 11317] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 Jun 2018 23:42:10 +0000 - rev 424085
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466366 [wpt PR 11317] - Update wpt metadata, a=testonly wpt-pr: 11317 wpt-type: metadata
fae61b46d4b5f119d208850c8a29f02d63cdbb3a: Bug 1466366 [wpt PR 11317] - Experimental Priority Hints support on fetch() API, a=testonly
Dominic Farolino <domfarolino@gmail.com> - Mon, 25 Jun 2018 21:49:04 +0000 - rev 424084
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466366 [wpt PR 11317] - Experimental Priority Hints support on fetch() API, a=testonly Automatic update from web-platform-testsExperimental Priority Hints support on fetch() API Adding support for Priority Hints on the fetch() API under an experimental flag. This adds the notion of importance to core/fetch code, and adds a new member to the RequestInit dictionary to communicate developer-specified "importance" downstream. R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws Bug: 821464 Change-Id: Ib96a128d77004029e86122c07552250c697dea5f Reviewed-on: https://chromium-review.googlesource.com/1084063 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Commit-Queue: Dominic Farolino <domfarolino@gmail.com> Cr-Commit-Position: refs/heads/master@{#564410} -- wpt-commits: dae7535c0428fbf057a5c39f324d5a3f47ba64c7 wpt-pr: 11317
74a21375a7d98075c18ae809c2182f6566b4fe0c: Bug 1466752 [wpt PR 11339] - HTML: Change <td hidden> and <th hidden> to expect display: none, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 25 Jun 2018 21:47:37 +0000 - rev 424083
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466752 [wpt PR 11339] - HTML: Change <td hidden> and <th hidden> to expect display: none, a=testonly Automatic update from web-platform-testsHTML: Change <td hidden> and <th hidden> to expect display: none Follows https://github.com/whatwg/html/pull/3736. -- wpt-commits: b20cb44c2991d09cc4c6e87260221cb777c15ef5 wpt-pr: 11339
148cd8a91deeb42f624ed413cf367802b80a94c8: Bug 1466710 [wpt PR 11334] - [wptrunner] End Sauce Connect process gracefully, a=testonly
jugglinmike <mike@mikepennisi.com> - Mon, 25 Jun 2018 21:46:22 +0000 - rev 424082
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466710 [wpt PR 11334] - [wptrunner] End Sauce Connect process gracefully, a=testonly Automatic update from web-platform-tests[wptrunner] End Sauce Connect process gracefully (#11334) Previously, the Sauce Connect process was closed gracefully in response to prolonged period of inactivity. This procedure was not used under normal operating conditions. Factor graceful shutdown logic into a new method, `quit`, and reuse this method to end the process following successful test completion. -- wpt-commits: 2bd11b91d490ddd5237bcb6d8149a7f25faaa101 wpt-pr: 11334
8a788ec47a1ea96c524db7133c978b0d7c8f910c: Bug 1466741 [wpt PR 11338] - Revert "WaveShaper must output non-zero values even if input is silent", a=testonly
Matt Giuca <mgiuca@chromium.org> - Mon, 25 Jun 2018 21:45:05 +0000 - rev 424081
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466741 [wpt PR 11338] - Revert "WaveShaper must output non-zero values even if input is silent", a=testonly Automatic update from web-platform-testsRevert "WaveShaper must output non-zero values even if input is silent" This reverts commit 325b492fe733ba4c8b2128069a0a232fea1789e3. Reason for revert: Broke webaudio/.../waveshaper-364379.html in webkit_layout_tests. See https://crbug.com/849535 Original change's description: > WaveShaper 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} TBR=rtoy@chromium.org,hongchan@chromium.org Change-Id: I29fd96b1a9dd2b87db12867031399b069beba706 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 807301, 849535 Reviewed-on: https://chromium-review.googlesource.com/1086647 Reviewed-by: Matt Giuca <mgiuca@chromium.org> Commit-Queue: Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#564359} -- wpt-commits: fa5ee47808411c866d09ad6a34dccf383b097bca wpt-pr: 11338
6d6bfe66dde6f140029f4d295642421ebc24c4c9: Bug 1466289 [wpt PR 11312] - custom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded, a=testonly
Justin Ribeiro <justin@justinribeiro.com> - Mon, 25 Jun 2018 21:43:47 +0000 - rev 424080
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1466289 [wpt PR 11312] - custom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded, a=testonly Automatic update from web-platform-testscustom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded createElement('my-element', undefined) was not being upgraded, though both createElement('my-element') and createElement('my-element', {}) were. Bug: 841725 Change-Id: Id43b21f8e1cad10745dedf3699691da7ad85cf03 Reviewed-on: https://chromium-review.googlesource.com/1084007 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#564352} -- wpt-commits: 8a5301b16f5e913bf9ffbb7d76abfda9d2435af2 wpt-pr: 11312
402bbf78b4cc295accf2eec2623f648521c5545a: Bug 1460771 [wpt PR 10958] - Compute correct sticky box constraints within scrollable containers, a=testonly
Yi Gu <yigu@chromium.org> - Mon, 25 Jun 2018 21:42:20 +0000 - rev 424079
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1460771 [wpt PR 10958] - Compute correct sticky box constraints within scrollable containers, a=testonly Automatic update from web-platform-testsCompute correct sticky box constraints within scrollable containers Currently calculating the skipped offset between sticky and its containing block assumes that the latter is not scrollable. However, when it is we should ignore the scroll offset from the container otherwise scrolling the container would cause the sticky offset incorrectly double accumulated. Bug: 841551 Change-Id: Ib49aaa74808847dcf6fce7dc0db9ac4d2de06c64 Reviewed-on: https://chromium-review.googlesource.com/1054488 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#564276} -- wpt-commits: dc60bfc45b49e3a5e653320e65b0fd447676b836 wpt-pr: 10958
a401456c4b11fd868a673a6b5ca6d63b0792b221: 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 424078
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1465045 [wpt PR 11223] - Update wpt metadata, a=testonly wpt-pr: 11223 wpt-type: metadata
0db160d046d156188429caaa739d0cfc2f0729d1: 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 424077
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +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
9c49cfec2e80f047ec53a1090c7036988efc3856: 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 424076
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +0000
Bug 1459354 [wpt PR 10857] - Update wpt metadata, a=testonly wpt-pr: 10857 wpt-type: metadata
168b53cc798241668866b9a47543aadb0e2e4df8: 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 424075
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +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
07c67995b90cf355e9a68fac3194ffca16b15a2b: 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 424074
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +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
17296e74b59b2392eca44b1528ce2db65b2dedc7: 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 424073
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +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
0c3f14124989fa35a8ff4f27863ab3bc32e633cb: 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 424072
Push 34198 by csabou@mozilla.com at Thu, 28 Jun 2018 10:05:18 +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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip