12ab4712761393918be4595367bc31bf0bd54ece: Bug 1489445 [wpt PR 12894] - [css-text] A leading white-space should break before handling overflow, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Tue, 09 Oct 2018 04:13:51 +0000 - rev 498661
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1489445 [wpt PR 12894] - [css-text] A leading white-space should break before handling overflow, a=testonly Automatic update from web-platform-tests[css-text] A leading white-space should break before handling overflow Leading white-spaces are indeed breaking opportunities that should prevent, if there are no other css properties forcing it, breaking text in the middle of a word when honoring the word-wrap/overflow-wrap CSS property. We are doing so if the leading white-space sequence is longer than 1 character, but when we have a single leading white-space, we are missing that breaking opportunity and we may lead to cases, like the one described in the bug. The root cause of the issue with single leading white-space breaking opportunities is that the RewindToMidWordBreak expects certain width to be committed in order to choose opportunities in previous runs if none of the ones detected by the ICU LazyLineBreakIterator prevents the overflow. However, this breaking opportunity should be considered together with other provided by the word-break CSS property (eg, break-word or break-all), as it was agreed in the discussion [1] with the CSS WG. This CL solves the issue identifying the single leading white-space braking opportunity in a new class field flag, and using it to consider this opportunity inside the mid-word breaking logic, or prevent to run it completely in the cases where 'break-all' is not set. This is basically a reland of 6ea2a2e7f3ef01e0c98424ce272a732ade92ad1a but with some changes to avoid regressions like the one reported in issue #866109. [1] https://github.com/w3c/csswg-drafts/issues/2907 Bug: 854624 Change-Id: I1cc0f55050d54ea1e76c655cf6b3ef8bcc0b0e2c Reviewed-on: https://chromium-review.googlesource.com/c/1209745 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#596406} -- wpt-commits: e201d802a5cb75d4cf618b8f5e1efe0e34c4ba3b wpt-pr: 12894
bd3bcc96361ce2cb1ed39a75c183f47fcee97376: Bug 1496102 [wpt PR 13337] - Python 3: Encode text content in Response.iter_content()., a=testonly
Ms2ger <Ms2ger@gmail.com> - Tue, 09 Oct 2018 04:13:49 +0000 - rev 498660
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1496102 [wpt PR 13337] - Python 3: Encode text content in Response.iter_content()., a=testonly Automatic update from web-platform-testsPython 3: Encode text content in Response.iter_content(). -- wpt-commits: a49e7638c45072077a92916ae41a26873e15d59a wpt-pr: 13337
15045982171d102c1d06208a2e4c0c98cc3dc947: Bug 1496142 [wpt PR 13339] - Switch WebKit browser product to WebDriver executors, a=testonly
Žan Doberšek <zan@falconsigh.net> - Tue, 09 Oct 2018 04:13:48 +0000 - rev 498659
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1496142 [wpt PR 13339] - Switch WebKit browser product to WebDriver executors, a=testonly Automatic update from web-platform-testsSwitch WebKit browser product to WebDriver executors (#13339) Switch away from Selenium executors to WebDriverTestharnessExecutor and WebDriverRefTestExecutor for the WebKit browser product. The browserVersion value is hard-coded to the 2.20 release series for the GTK+ port of WebKit as that's when the WebDriver functionality was introduced. -- wpt-commits: dc97ad5a7865a4849678baf67c380a3cc7bb420b wpt-pr: 13339
fedfac60200e8e25d08f1bec463b62589d8d4d53: Bug 1495935 [wpt PR 13321] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 03 Oct 2018 04:57:16 +0000 - rev 498658
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495935 [wpt PR 13321] - Update wpt metadata, a=testonly wpt-pr: 13321 wpt-type: metadata
32e2bba388814b034c661c290e561e51efc31f5a: Bug 1495935 [wpt PR 13321] - Include ended tracks when cloning MediaStreams., a=testonly
Guido Urdaneta <guidou@chromium.org> - Tue, 09 Oct 2018 04:13:43 +0000 - rev 498657
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495935 [wpt PR 13321] - Include ended tracks when cloning MediaStreams., a=testonly Automatic update from web-platform-testsInclude ended tracks when cloning MediaStreams. This CL also covers the MediaStream constructor. In addition, tests are moved to WPT. Bug: 770908 Change-Id: I6db9a86e9ee839efc2b04b00ae8fc57f07d852c3 Reviewed-on: https://chromium-review.googlesource.com/c/1256796 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#596247} -- wpt-commits: 425430423cbe2cc78a34b2e4732a0d4361052219 wpt-pr: 13321
bb8a619658078f2cdc43c964d4779b5b5b6aeb33: Bug 1495968 [wpt PR 13322] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 03 Oct 2018 08:04:38 +0000 - rev 498656
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495968 [wpt PR 13322] - Update wpt metadata, a=testonly wpt-pr: 13322 wpt-type: metadata
50a6846cd5cc91d5e61ed9c802723704e22f64c8: Bug 1495968 [wpt PR 13322] - Remove and fix non-spec compliant WebRTC tests, a=testonly
Florent Castelli <orphis@chromium.org> - Tue, 09 Oct 2018 04:13:38 +0000 - rev 498655
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495968 [wpt PR 13322] - Remove and fix non-spec compliant WebRTC tests, a=testonly Automatic update from web-platform-testsRemove and fix non-spec compliant WebRTC tests Bug: 803494 Change-Id: Ic9efe4adba6909f6af3dbcf90d64debeef216480 Reviewed-on: https://chromium-review.googlesource.com/c/1257786 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#596244} -- wpt-commits: ca3d628ad63e6a1f4a818d6280dfb4aac344f6a7 wpt-pr: 13322
45d93015bb0295ea2e8f2c2ec719e26ed2253c24: Bug 1496271 [wpt PR 2103] - Add test to verify scroll restoration order in history traversal, a=testonly
smaug---- <smaug----@users.noreply.github.com> - Tue, 09 Oct 2018 04:13:36 +0000 - rev 498654
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1496271 [wpt PR 2103] - Add test to verify scroll restoration order in history traversal, a=testonly Automatic update from web-platform-testsMerge pull request #2103 from majido/scroll-restoration-order Add test to verify scroll restoration order in history traversal -- wpt-commits: 656382714083382c32a5e8df57a3fe07cb06b4b2 wpt-pr: 2103
bb93c91a609e4bb76483ae56dd105d9b01cf7ec3: Bug 1491592 [wpt PR 13017] - Use the voiceschanged event to wait for SpeechSynthesisVoice instance, a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 09 Oct 2018 04:13:34 +0000 - rev 498653
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1491592 [wpt PR 13017] - Use the voiceschanged event to wait for SpeechSynthesisVoice instance, a=testonly Automatic update from web-platform-testsUse the voiceschanged event to wait for SpeechSynthesisVoice instance (#13017) In https://github.com/web-platform-tests/wpt/pull/12317 I noticed that speechSynthesis.getVoices() could return an empty list and is allowed to do so by spec, but not that there's also an event that's fired when the voices are updated: https://w3c.github.io/speech-api/#eventdef-speechsynthesis-voiceschanged Using this improves coverage somewhat. -- wpt-commits: 2d49b1ea2fb2c46765ef5bdb01e287497a7406a9 wpt-pr: 13017
7f31d10746338bd7b0501bc3f02669d031d96f2b: Bug 1495976 [wpt PR 13323] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 03 Oct 2018 08:22:07 +0000 - rev 498652
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495976 [wpt PR 13323] - Update wpt metadata, a=testonly wpt-pr: 13323 wpt-type: metadata
65afc37288c9a57b7c1c4139a6ad78870434684e: Bug 1495976 [wpt PR 13323] - Reland: Implement RTCIceTransport.onselectedcandidatepairchange, a=testonly
Steve Anton <steveanton@chromium.org> - Tue, 09 Oct 2018 04:13:30 +0000 - rev 498651
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495976 [wpt PR 13323] - Reland: Implement RTCIceTransport.onselectedcandidatepairchange, a=testonly Automatic update from web-platform-testsReland: Implement RTCIceTransport.onselectedcandidatepairchange TBR=hta@chromium.org,haraken@chromium.org Bug: 864871 Change-Id: I6a2e0dc98efc58e22b33066ee3d37ded3c9b021a Reviewed-on: https://chromium-review.googlesource.com/c/1258503 Commit-Queue: Steve Anton <steveanton@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#596207} -- wpt-commits: efa4c0d1048c6f1e2aae98a8be295eea689fb6fe wpt-pr: 13323
9c5df0a2afe5deb235a4508a43da64baefa0c695: Bug 1495986 [wpt PR 13325] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 03 Oct 2018 09:45:33 +0000 - rev 498650
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495986 [wpt PR 13325] - Update wpt metadata, a=testonly wpt-pr: 13325 wpt-type: metadata
4ed3b308efc22ee34d57c9b926b9b82c6671f558: Bug 1495986 [wpt PR 13325] - AppCache: Add WPTs for AppCache on iframes, a=testonly
Hiroki Nakagawa <nhiroki@chromium.org> - Tue, 09 Oct 2018 04:13:25 +0000 - rev 498649
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495986 [wpt PR 13325] - AppCache: Add WPTs for AppCache on iframes, a=testonly Automatic update from web-platform-testsAppCache: Add WPTs for AppCache on iframes Cq-Include-Trybots: luci.chromium.try​:linux_mojo Change-Id: I6933b37bf1e876f5c622876dd1c84ff830436c6a Bug: n/a Reviewed-on: https://chromium-review.googlesource.com/c/1245341 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#596119} -- wpt-commits: 5783f415ebbf2c9199f5d1b0b791fe425e61f57e wpt-pr: 13325
3b573a0ec2a1c250083bc0273f36b158408b5ffb: Bug 1495812 [wpt PR 13318] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 02 Oct 2018 22:30:46 +0000 - rev 498648
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495812 [wpt PR 13318] - Update wpt metadata, a=testonly wpt-pr: 13318 wpt-type: metadata
1c32e75346371ae46f30e3a14332736d310bb925: Bug 1495812 [wpt PR 13318] - Align more closely with Gecko for clip-path reference box., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Tue, 09 Oct 2018 04:13:20 +0000 - rev 498647
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495812 [wpt PR 13318] - Align more closely with Gecko for clip-path reference box., a=testonly Automatic update from web-platform-testsAlign more closely with Gecko for clip-path reference box. This changes how we calculate the reference box when the layout box is a non-atomic inline. It was very broken for LayoutNG; we just set the height to 0. For legacy layout we used the width of the bounding box for all lines and the height of the first fragment. Instead, consistently use the size of the first fragment, in both NG and legacy. Also get it right if writing-mode is vertical-rl. Bug: 641907 Cq-Include-Trybots: luci.chromium.try​:linux_layout_tests_layout_ng;luci.chromium.try​:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I652f197bc3d950fad1bf6067dc5f38c2df72a0a3 Reviewed-on: https://chromium-review.googlesource.com/c/1256808 Reviewed-by: Fredrik Söderquist <fs@opera.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#596110} -- wpt-commits: 123dbad2221a34797cd146cbaeaff50c04c6dded wpt-pr: 13318
fac19da70365eef8f8ab927f154523b11a089104: Bug 1496205 [wpt PR 13343] - Fix wpt/css/css-masking/mask-svg-content/mask-text-001.svg, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 09 Oct 2018 04:13:18 +0000 - rev 498646
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1496205 [wpt PR 13343] - Fix wpt/css/css-masking/mask-svg-content/mask-text-001.svg, a=testonly Automatic update from web-platform-testsFix wpt/css/css-masking/mask-svg-content/mask-text-001.svg The test has fixed dimensions of 100x100 pixels - the reference does not. Add same fixed dimensions to the reference to get the same clipping behavior. Bug: 890755 Change-Id: Ib3d12ad1f7ace05027b81b9c683158490ae116ab Reviewed-on: https://chromium-review.googlesource.com/1256568 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#595936} -- wpt-commits: eaed217d2c3ed8250b585f5b56751e1d84b7e502 wpt-pr: 13343
daf57bccbbdcb3067db8c4883e85a509949c3225: Bug 1495477 [wpt PR 13287] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 01 Oct 2018 20:55:17 +0000 - rev 498645
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495477 [wpt PR 13287] - Update wpt metadata, a=testonly wpt-pr: 13287 wpt-type: metadata
ec2733b0a08fcfed54c2f0dfd344036900ac1e4b: Bug 1495477 [wpt PR 13287] - Implement RTCQuicTransport.onquicstream and stream reset/finish, a=testonly
Steve Anton <steveanton@chromium.org> - Tue, 09 Oct 2018 04:13:12 +0000 - rev 498644
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495477 [wpt PR 13287] - Implement RTCQuicTransport.onquicstream and stream reset/finish, a=testonly Automatic update from web-platform-testsImplement RTCQuicTransport.onquicstream and stream reset/finish This CL implements the RTCQuicTransport createStream method and the corresponding quicstream event hooked up to the QUIC adapters. It also implements RTCQuicStream.reset/finish and statechange event to allow end-to-end testing. Bug: 874296 Change-Id: I331d37f3e21c606697b8768bf9eea59c90487163 Reviewed-on: https://chromium-review.googlesource.com/c/1217846 Commit-Queue: Steve Anton <steveanton@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#596068} -- wpt-commits: 2625aa78ed1abccb12cde20af2b5d6650a407cf6 wpt-pr: 13287
578584d3e8e54f6080253acc575231460ca17e0c: Bug 1495790 [wpt PR 13316] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 02 Oct 2018 21:40:09 +0000 - rev 498643
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495790 [wpt PR 13316] - Update wpt metadata, a=testonly wpt-pr: 13316 wpt-type: metadata
6da27d08b97b8245c0ea7596dd7e6a6b88e7b88a: Bug 1495790 [wpt PR 13316] - sensors: Ensure a document without an associated frame does not crash, a=testonly
Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> - Tue, 09 Oct 2018 04:13:07 +0000 - rev 498642
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495790 [wpt PR 13316] - sensors: Ensure a document without an associated frame does not crash, a=testonly Automatic update from web-platform-testssensors: Ensure a document without an associated frame does not crash Commit d1034e1e6 ("sensors: Make SensorProviderProxy supplement Document, not LocalFrame") tied a sensor's lifetime to a document rather than a frame, but we continued to assume Document::GetFrame() would never return null. This is not true, as evidenced by the crash reports in bug 889754, caused by SensorProxy::ShouldSuspendUpdates() trying to invoke methods on a LocalFrame that can actually be a nullptr. The original backtrace in the bug report seems to come from sensor creation, but it is easier to trigger the same crash with a focus change after destroying a sensor's document's frame. Bug: 861675, 889754 Change-Id: Idb9ed5c18a655e113e2fb76cde6615aeefcc544a Reviewed-on: https://chromium-review.googlesource.com/1256826 Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Raphael Kubo da Costa (CET) <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#595958} -- wpt-commits: 27d87552c9a67481fb2d6ca82a71622c24ce7090 wpt-pr: 13316
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip