e1ddc06a718228715000655afb410f0035c4ced0: Bug 1514676 [wpt PR 14556] - [css-text] Typo in Thai text, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 19 Dec 2018 12:09:43 +0000 - rev 512163
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514676 [wpt PR 14556] - [css-text] Typo in Thai text, a=testonly Automatic update from web-platform-tests [css-text] Typo in Thai text Since we're testing dictionary based word-boundary detection, it seems quite important to avoid spelling mistakes. The Thai word “and” is spelled “และ” and not “แและ”. -- wpt-commits: 81f23a9e43fc5ae0a06b59609c88959a7363c66a wpt-pr: 14556
95e4f2c6774a5dcb2cb229247c72f25c9895b893: Bug 1514674 [wpt PR 14555] - [css-text] Fix test, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 19 Dec 2018 12:09:41 +0000 - rev 512162
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514674 [wpt PR 14555] - [css-text] Fix test, a=testonly Automatic update from web-platform-tests [css-text] Fix test It used an incorrect flag (ahem), and the description sentence was ambiguous. -- wpt-commits: 0065f28dbff10c61e73a9e0a60b81675f9d32e83 wpt-pr: 14555
f99452e8b46041a428a9f8513b69a4784b5d4a28: Bug 1514659 [wpt PR 14550] - Delete test that can never fail, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 19 Dec 2018 12:09:39 +0000 - rev 512161
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514659 [wpt PR 14550] - Delete test that can never fail, a=testonly Automatic update from web-platform-tests Delete tests that can never fail These tests claims to test overflow-wrap, but it never overflows, so the property never gets the chance to do anything. The description is also confusing, as it asks the reviewer to check things that cannot be seen visually: whether the black box is one or two rows cannot be seen, since they are contiguous. -- wpt-commits: 75f54944ed436a05802a310b101d74732f95cd28 wpt-pr: 14550
030974f99191feb97b4b625f1476945dcb64d1a3: Bug 1514650 [wpt PR 14547] - Remove incorrect tests, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 19 Dec 2018 12:09:37 +0000 - rev 512160
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514650 [wpt PR 14547] - Remove incorrect tests, a=testonly Automatic update from web-platform-tests Remove incorrect tests Both these tests will render incorrectly if a specific font isn't available, and they don't install it themselves, making them misleading. Moreover, word-break-break-all-009's reference is just a copy of the test, and relies on automatic line breaking instead of manually inserted <br>s, so it will always pass. Finally, these tests could be fixed, but they are testing things that are already covered by other tests, so deleting them is appropriate. -- wpt-commits: a22f78b49f0f2ab2198bd97be961a777473b68ab wpt-pr: 14547
7b3a9d543fa3970a534623af923d4e2d77aa834d: Bug 1514654 [wpt PR 14548] - Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd, a=testonly
Andrew Comminos <acomminos@fb.com> - Wed, 19 Dec 2018 12:09:35 +0000 - rev 512159
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514654 [wpt PR 14548] - Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd, a=testonly Automatic update from web-platform-tests Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd When simulating a delay after a statusline, measure that the delay is not included in the TTFB by measuring that it occurred between responseStart and responseEnd rather than requestStart and responseStart. This makes the tests less flaky when subject to shaky network and thread scheduling conditions, as might be present using Firefox's chaos mode. Bug: 568024 Change-Id: I0356f6256af6bc87fbb14860ed05472526c03e5d Reviewed-on: https://chromium-review.googlesource.com/c/1377725 Reviewed-by: Yoav Weiss <yoav@yoav.ws> Commit-Queue: Andrew Comminos <acomminos@fb.com> Cr-Commit-Position: refs/heads/master@{#617021} -- wpt-commits: 7275e40d9bc2a6cebec14f29a4993334bb208ed8 wpt-pr: 14548
d102ed7e2f5e5dc4c25af133be3bae0e0c9d8c42: Bug 1513443 [wpt PR 14472] - Add WPT to verify that 1XX responses are used to provide responseStart timing, a=testonly
Andrew Comminos <acomminos@fb.com> - Wed, 19 Dec 2018 12:09:33 +0000 - rev 512158
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1513443 [wpt PR 14472] - Add WPT to verify that 1XX responses are used to provide responseStart timing, a=testonly Automatic update from web-platform-tests Add WPT to verify that 1XX responses are used to provide responseStart timing Verifies that the UA sets responseStart to the time that an initial 1XX response was received by returning {100, delay, 200} and testing that the delay is not included in responseStart. Bug: 568024 Change-Id: I7295e6478a95abe1b6154ddf1feab764f596a5ec Reviewed-on: https://chromium-review.googlesource.com/c/1372359 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#615853} -- wpt-commits: 6d3120bad3e5d55bfebb3063a5ef04e7fc231905 wpt-pr: 14472
ce83501a41ddc819a6ece865ac8f964b7f0bf5d1: Bug 1514647 [wpt PR 14546] - Remove unneeded tests, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 19 Dec 2018 12:09:31 +0000 - rev 512157
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514647 [wpt PR 14546] - Remove unneeded tests, a=testonly Automatic update from web-platform-tests Remove unneeded tests These 4 tests are not technically wrong, but they are not automated, and they don't cover any aspect of the spec that isn't already covered by other tests. -- wpt-commits: 1a70ecd97624eb434a602948227cb7c998bde716 wpt-pr: 14546
625c6152a40cbe9039035a9e598f582cd49412ae: Bug 1514576 [wpt PR 14545] - Update <button type="menu"> test to reflect its removal, a=testonly
Zirro <code@zirro.se> - Wed, 19 Dec 2018 12:09:29 +0000 - rev 512156
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514576 [wpt PR 14545] - Update <button type="menu"> test to reflect its removal, a=testonly Automatic update from web-platform-tests Update <button type="menu"> test to reflect its removal <button type="menu"> got removed in https://github.com/whatwg/html/pull/2342 and this test was failing in all browsers. -- wpt-commits: 11971ac2161859001b861630338c0e47fee1b59a wpt-pr: 14545
8375b7606b0ebd068678d4f17722bbb30c0b14e4: Bug 1514410 [wpt PR 14529] - Fix gradient background sizing, a=testonly
Stephen Chenney <schenney@chromium.org> - Wed, 19 Dec 2018 12:09:27 +0000 - rev 512155
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514410 [wpt PR 14529] - Fix gradient background sizing, a=testonly Automatic update from web-platform-tests Fix gradient background sizing This is a hard-to-fix situation. We size generated background images according to the tile size, which is a snapped rectangle sized according to the destination values, in general. But then we compute a src rect for image drawing using the unsnapped values, because that is best for bitmap images where we want to pull out the most accurate src rect possible. However, that source rect ends up larger than the tile size due to rounding without the original offset in the layer (because now we are working in image space). The gradient painting code then sees that it has a src rect that is larger than the tile size and hence the gradient image size. The code thinks that we want to have some more pixels than the gradient provides, which is true in some cases, and scales things to get those extra pixels in the painted output. Hence empty pixels on the screen when we really want the gradient to be filling the dest rect. Changing the gradient painting code will break valid use cases. Changing the tile size breaks things in a different way and doesn't really fix the problem. So change the src rect computation to use snapped sizes for generated content in an attempt to get a src that matches the tile size. R=fmalita@chromium.org Bug: 898950 Change-Id: I100575ad4f4fa3004fbc232a72c90b0032ccef4e Reviewed-on: https://chromium-review.googlesource.com/c/1376814 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by: Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#616944} -- wpt-commits: fcb8094864e059a942cadbdb839794182b309dc8 wpt-pr: 14529
a2b2c1fa37b33ff14f5cfa3b548bc2dc105b73f6: Bug 1514099 [wpt PR 14510] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 09:45:10 +0000 - rev 512154
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514099 [wpt PR 14510] - Update wpt metadata, a=testonly wpt-pr: 14510 wpt-type: metadata
990811660670a3569923e20aee0c4a4ee541ae4d: Bug 1514099 [wpt PR 14510] - Update for RTCQuicStream.write() function., a=testonly
Seth Hampson <shampson@chromium.org> - Wed, 19 Dec 2018 12:09:22 +0000 - rev 512153
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514099 [wpt PR 14510] - Update for RTCQuicStream.write() function., a=testonly Automatic update from web-platform-tests Update for RTCQuicStream.write() function. Combines functionality of finish() into write() by adding a new QuicStreamWriteParameters input parameter that includes a finish boolean. This is consistent with the latest spec draft and also adds symmetry between readInto() and write(). Bug: 874296 Change-Id: I0def0ca25587ebf00a4b179ce8e9e7a124c818f6 Reviewed-on: https://chromium-review.googlesource.com/c/1376720 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Steve Anton <steveanton@chromium.org> Commit-Queue: Seth Hampson <shampson@chromium.org> Cr-Commit-Position: refs/heads/master@{#616941} -- wpt-commits: a3efcf10006556ecb6169610324f650a5522650d wpt-pr: 14510
5395db370569cbf4988ce37b4f3016d5cfbcb2b9: Bug 1514432 [wpt PR 14530] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 15 Dec 2018 14:13:11 +0000 - rev 512152
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514432 [wpt PR 14530] - Update wpt metadata, a=testonly wpt-pr: 14530 wpt-type: metadata
4bfef6168f182fd75312c7194bb26b7441188442: Bug 1514432 [wpt PR 14530] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706, a=testonly
youennf <youennf@users.noreply.github.com> - Wed, 19 Dec 2018 12:09:17 +0000 - rev 512151
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514432 [wpt PR 14530] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706 (#14530) -- wpt-commits: e183d8671bde035c7a0168a75119a5f80bd592cb wpt-pr: 14530
86ca0a729bfcfa8a0d8c0e223fd6285b682bb600: Bug 1513766 [wpt PR 14486] - [CSS Transitions] Add test for reparenting, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 19 Dec 2018 12:09:15 +0000 - rev 512150
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1513766 [wpt PR 14486] - [CSS Transitions] Add test for reparenting, a=testonly Automatic update from web-platform-tests [CSS Transitions] Add test for reparenting As per https://github.com/w3c/csswg-drafts/issues/3309, any CSS Transition on a reparented element should be cancelled, as it leaves and then re-enters the Document. This already works on Chrome, Firefox, and Safari but fails on Edge. Bug: 902328 Change-Id: I097675a8146c8047417dd48193d0747216418cfb Reviewed-on: https://chromium-review.googlesource.com/c/1374742 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#616830} -- wpt-commits: cf8b055289c68215fd4a3274c94d0f5484c27dd3 wpt-pr: 14486
a56d3fa354af52ee057e09349d5b0c744af24099: Bug 1514102 [wpt PR 14511] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 10:06:14 +0000 - rev 512149
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514102 [wpt PR 14511] - Update wpt metadata, a=testonly wpt-pr: 14511 wpt-type: metadata
bfd4b93ba923d4bb6746f8246656974c432ed785: Bug 1514102 [wpt PR 14511] - [UserTiming] Fix mark-measure-return-null test, a=testonly
Nicolas Pena <npm@chromium.org> - Wed, 19 Dec 2018 12:09:10 +0000 - rev 512148
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514102 [wpt PR 14511] - [UserTiming] Fix mark-measure-return-null test, a=testonly Automatic update from web-platform-tests [UserTiming] Fix mark-measure-return-null test The test was incorrect per L2 spec: a void method 'returns' an undefined value, not a null object. This CL changes the test to show how to perform feature detection and compares L2 and L3 behavior. Bug: 914441 Change-Id: Id7173b2693d5bd42013dcdd25266d64fa8956e6a -- Merge pull request #14511 from web-platform-tests/chromium-export-cl-1377129 [UserTiming] Fix mark-measure-return-null test -- wpt-commits: 1dd43edb91fa86dbda5af3a9675e3b103c9e8cd0, ca3a8d6d2de5be8dac1daa17126d8f30d1489c95 wpt-pr: 14511
58bbc72bb0ff922171edbc4458b8703cc9808935: Bug 1514001 [wpt PR 14506] - Reland Make testharness tests run in a top-level browsing context , a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 19 Dec 2018 11:52:20 +0000 - rev 512147
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514001 [wpt PR 14506] - Reland Make testharness tests run in a top-level browsing context , a=testonly Automatic update from web-platform-tests Make testharness tests run in a top-level browsing context Traditionally testharness tests ran in a auxillary browsing context opened using window.open and with access to the opener. This works well because the long-lived nature of the opener helps to avoid some of the race conditions that would otherwise occur. But it doesn't work *that* well; the recent refactor to stop continually focusing the opener broke tests that alter document.domain or otherwise prevent the opener being same-domain with the test window. And future platform features may cause the opener to be nulled out entirely so even a postMessage based fix wouldn't work. To solve all of this, this patch refactors things so that the initial window doesn't contain any logic at all and is just used to keep the browser alive between tests. Most of the logic moves to testharnessreport.js which is loaded once per test. In order to get the right timeout when timeout_multiplier is set this requires an addition to the product API in wptrunner to expose a function for getting the timeout multiplier. This allows us to get the timeout_multiplier for testharness tests upfront and avoids the need to change the content of testharnessreport when we start running testharness tests, or to restart the server for each test type. The main issue with the single-window implementation is that we need to start injecting script once the test page has loaded testharnessreport.js. For most browsers we are able to use pageLoadStrategy=eager to control this; in that case we can start running tests once DOMContentLoaded is reached. Chrome doesn't support this pageLoadStrategy, however, so we have to fake support with custom script. -- Ensure we call __wptrunner_process_next_event whenever we put a message on the queue -- wpt-commits: e4ba26cf0324af4ffd46607b296f5362243728a3, f6c42824add97dac84434c92c606aacd867c3534 wpt-pr: 14506
7d98c8a039785005556251fe5d4b7dcaa4050a27: Bug 1514355 [wpt PR 14525] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 20:14:11 +0000 - rev 512146
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514355 [wpt PR 14525] - Update wpt metadata, a=testonly wpt-pr: 14525 wpt-type: metadata
5b91140384aa46aaf31c87d28b19bbdb30b2e3e5: Bug 1514355 [wpt PR 14525] - [LayoutTest] Split animations-parsing.html into two tests, a=testonly
Xida Chen <xidachen@chromium.org> - Wed, 19 Dec 2018 11:39:11 +0000 - rev 512145
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514355 [wpt PR 14525] - [LayoutTest] Split animations-parsing.html into two tests, a=testonly Automatic update from web-platform-tests [LayoutTest] Split animations-parsing.html into two tests Currently it tests both style.animation and getComputedStyle.animation. This CL splits the test into two tests, one for style.animation, and the other one for getComputedStyle.animation such that each test is minimal. Bug: 772852 Change-Id: I3c3f43305497ffe9d91c4e3806efe2e65ff17806 Reviewed-on: https://chromium-review.googlesource.com/c/1378230 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#616677} -- wpt-commits: 3a8ff1cd2f78d58de6ddf4ac0fe13e72e6502229 wpt-pr: 14525
ba204a073a2338fa4f26e97c72361a14d78280a1: Bug 1514365 [wpt PR 14527] - Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 19 Dec 2018 11:39:09 +0000 - rev 512144
Push 10566 by archaeopteryx@coole-files.de at Mon, 28 Jan 2019 12:41:12 +0000
Bug 1514365 [wpt PR 14527] - Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html, a=testonly Automatic update from web-platform-tests Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html Attempt to stabilize in Gecko. Bug: 626744 Change-Id: Idfa06176948d1ffaf6ba8e65263bf5818ffd321b Reviewed-on: https://chromium-review.googlesource.com/c/1375875 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#616543} -- wpt-commits: 4559dab34174df979b5db4d3ba01429c03c06850 wpt-pr: 14527
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip