5999464804d54d48e0f86663ec2fc4fc47c41696: Bug 1645216 [wpt PR 24122] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 17 Jun 2020 13:14:27 +0000 - rev 536823
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645216 [wpt PR 24122] - Update wpt metadata, a=testonly wpt-pr: 24122 wpt-type: metadata
8c46d41711c4c39505fc6303c203fb42a6b0b646: Bug 1645216 [wpt PR 24122] - Exclude non relevants reports from the COOP-opener-breakage tests., a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Mon, 22 Jun 2020 10:42:03 +0000 - rev 536822
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645216 [wpt PR 24122] - Exclude non relevants reports from the COOP-opener-breakage tests., a=testonly Automatic update from web-platform-tests Exclude non relevants reports from the COOP-opener-breakage tests. (#24122) Without this, several reports from COOP-access-reporting would show in between and cause most of the tests to fail. BUG=1090273 Change-Id: I360b82da4b6a2dcb0380dfa4dce5a678e6ad73a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235851 Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#776930} Co-authored-by: arthursonzogni <arthursonzogni@chromium.org> -- wpt-commits: 1f3fadc328924b3a105b34c2c47b1a3d2aafcbf3 wpt-pr: 24122
971c73c56b5a4bf4a860986fcc0d71503bb93d26: Bug 1645980 [wpt PR 24163] - [LayoutNG] Blocks with no same-flow breaks have perfect break appeal., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Mon, 22 Jun 2020 10:41:58 +0000 - rev 536821
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645980 [wpt PR 24163] - [LayoutNG] Blocks with no same-flow breaks have perfect break appeal., a=testonly Automatic update from web-platform-tests [LayoutNG] Blocks with no same-flow breaks have perfect break appeal. We used to only update the appeal of breaking inside a box when inserting an in-flow break, either before/inside an in-flow child, or inside the box itself (if its non-auto remaining block-size was too large to fit). What was missing was when the box itself could fit, and it only had parallel flow breaks. Without this fix, if a float broke inside a block, and the block itself didn't need a break for its own sake, we'd consider the break inside to be a last-resort break (so that we'd try our best to break earlier). Bug: 829028 Change-Id: I5cd5f05ea319a75186c7510bf40dd54b104160b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2245911 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#779244} -- wpt-commits: 6e8cf634241a641aadd39d02a291e7642ba2f248 wpt-pr: 24163
de01a9b4589f89b265435f593ba39a6af0b45321: Bug 1645711 [wpt PR 24142] - Fixes empty alt text on broken images overriding css dimensions., a=testonly
Yu Han <yuzhehan@chromium.org> - Mon, 22 Jun 2020 10:41:53 +0000 - rev 536820
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645711 [wpt PR 24142] - Fixes empty alt text on broken images overriding css dimensions., a=testonly Automatic update from web-platform-tests Fixes empty alt text on broken images overriding css dimensions. Prior to this CL, an img with CSS height, width and empty alt text renders as nothing. This is wrong because [2] states that the img should be rendered as a replaced element with its intrinsic dimensions. The fix continues from the previous fix to the img title attribute by adding an additional check to see if the alt text is empty too. [1] https://html.spec.whatwg.org/multipage/rendering.html#images-3::represents-2 Bug: 753868 Change-Id: I9b127c54d9d5eb0f1e900dee47f24aff09f2ed8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238327 Commit-Queue: Yu Han <yuzhehan@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Reviewed-by: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#779151} -- wpt-commits: 84e71a84b79199bc307866bbe0edcbcc7c4752ce wpt-pr: 24142
47738943414e4c7c1de33ac7ccee3f8d3043341c: Bug 1646117 [wpt PR 24169] - Adding a <media> into an inactive document should not crash., a=testonly
Nate Chapin <japhet@chromium.org> - Mon, 22 Jun 2020 10:41:46 +0000 - rev 536819
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646117 [wpt PR 24169] - Adding a <media> into an inactive document should not crash., a=testonly Automatic update from web-platform-tests Adding a <media> into an inactive document should not crash. Bug: 1092889 Test: html/semantics/embedded-content/the-audio-element/audio-appendChild-to-inactive-document-crash.html Change-Id: I14d78db39b74d4593f3ed71b8440ca108fafdd0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2247120 Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Nate Chapin <japhet@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#779148} -- wpt-commits: d09f4297ffcb031b1d6b789ed0deeaf16b12194b wpt-pr: 24169
a824c0e02cfd985e0dabbc1551b29193b79c6d0c: Bug 1641284 [wpt PR 23798] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 17 Jun 2020 04:03:54 +0000 - rev 536818
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1641284 [wpt PR 23798] - Update wpt metadata, a=testonly wpt-pr: 23798 wpt-type: metadata
2b3d5e91ef77dc3ec3db0016cb6b59a89313c011: Bug 1641284 [wpt PR 23798] - Fixes input image type fallback content to respect display property., a=testonly
Yu Han <yuzhehan@chromium.org> - Mon, 22 Jun 2020 10:41:38 +0000 - rev 536817
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1641284 [wpt PR 23798] - Fixes input image type fallback content to respect display property., a=testonly Automatic update from web-platform-tests Fixes input image type fallback content to respect display property. Prior to this CL, image input type will always use a Block layout when the image src can't be loaded. This prevents web developers from changing the layout via CSS display property. This CL fixes the issue by creating a Layout object based on the CSS computed styles. Web developers can change image's fallback text layout via CSS display property. If none is passed in, it defaults to inline-block, which is the default layout of the input image type. Spec: https://html.spec.whatwg.org/multipage/rendering.html#images-3:represents-5 Bug: 948066 Change-Id: I907432485472c472608b9d84d36fa2df29412f7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212963 Reviewed-by: Mason Freed <masonfreed@chromium.org> Commit-Queue: Yu Han <yuzhehan@chromium.org> Cr-Commit-Position: refs/heads/master@{#779108} -- wpt-commits: 06fdf531b436b283cb6bb0f4d33ceffb904a9184 wpt-pr: 23798
5e1ec38dd7a121a93b8831c899102e13d69fd377: Bug 1645712 [wpt PR 24143] - Fixes img without src but with title doesn't respect CSS dimensions., a=testonly
Yu Han <yuzhehan@chromium.org> - Mon, 22 Jun 2020 10:41:33 +0000 - rev 536816
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645712 [wpt PR 24143] - Fixes img without src but with title doesn't respect CSS dimensions., a=testonly Automatic update from web-platform-tests Fixes img without src but with title doesn't respect CSS dimensions. Prior to this CL, img with CSS height, width and a title attribute is treated as inline text without the CSS dimensions applied. The reason is that title attribute is treated as a backup for alt text [1]. Thus, this prevents the img to be treated as replaced element with intrinsic dimensions [2]:represents-2, but it's treated as non-replaced text [2]:represents-3 where the CSS dimensions are ignored. The fix is instead of checking the HTMLElement::AltText(), check only the presence of alt attribute when determining if the element should be treated as a replaced element. I had considered making the fix in [1] so that AltText() doesn't fallback to title. However, I decided against it to minimized the impact of this change and only fix it when the img doesn't represent an image and defaults to its fallback behavior. [1] https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/html/html_image_element.cc;l=321 [2] https://html.spec.whatwg.org/multipage/rendering.html#images-3 Bug: 958250 Change-Id: I78b3d84d8237b72505fdc5389702d119d61ae405 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2239473 Commit-Queue: Yu Han <yuzhehan@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Reviewed-by: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#779100} -- wpt-commits: 21698f651c777373dc6e89c5f0e3969237387fdc wpt-pr: 24143
fcb96ec497a6f4d5fd284bea46b80d4ebf7735b1: Bug 1642016 [wpt PR 23864] - Vectorize DelayNode processor for k-rate delays, a=testonly
Raymond Toy <rtoy@chromium.org> - Mon, 22 Jun 2020 10:41:28 +0000 - rev 536815
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1642016 [wpt PR 23864] - Vectorize DelayNode processor for k-rate delays, a=testonly Automatic update from web-platform-tests Vectorize DelayNode processor for k-rate delays Instead of processing the data one sample at a time, we can process a block at a time by doing large memcpy's and then some vector operations to interpolate the samples. As a final micro-optimization, if the interpolation factor is 0, we can skip the interpolation phase altogether. Using (a slightly modified) Spotify's Web Audio Bench, we have the following results using 500 runs of 10 sec each (the default) on a linux machine: Without CL: TEST μs MIN Q1 MEDIAN Q3 MAX MEAN STDDEV Baseline 594 594 740 751 761 3215 757.82 146.55 Delay-default 331 331 387 405 416 2124 406.47 81.65 Delay-0.1 344 344 401 423 440 834 425.68 41.04 DelayAutomation-a-rate 675 675 748 763 779 1262 768.23 42.97 DelayAutomation-k-rate 365 365 424 444 460 1036 446.24 38.61 With CL: TEST μs MIN Q1 MEDIAN Q3 MAX MEAN STDDEV Baseline 736 736 747 756 765 901 758.57 17.76 Delay-default 180 180 230 249 267 1467 256.75 77.1 Delay-0.1 233 233 302 317 332 2402 322.39 96.86 DelayAutomation-a-rate 612 612 683 698 713 983 701.78 33.85 DelayAutomation-k-rate 206 206 281 299 318 522 305.34 37.96 As we can see, the CL speeds up processing the default by 38%, delay-0.1 25% and k-rate by 32% (using the mean and not us results). One layout test needed to be updated to handle numerical differences for mac. The implementation of Vsma on mac is different from linux and windows. and this difference shows up in the test. (Mac uses VDSP_vsma, instead of our hand-written Vsma. VDSP_vsma might be using an FMA which has different round properties.) Bug: 1087071 Change-Id: I2b95096fef9fd1e5f7c87e4f4bdfa7d52f5b8d58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2171843 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#779062} -- wpt-commits: c4fef962c5d98c16f212f768896188824500d41b wpt-pr: 23864
04af5449d09e655bcd0cda458c4e851411b280bc: Bug 1645938 [wpt PR 24159] - [TransformInterop] Always consider main-thread layers visible for cc, a=testonly
Chris Harrelson <chrishtr@chromium.org> - Mon, 22 Jun 2020 10:41:23 +0000 - rev 536814
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645938 [wpt PR 24159] - [TransformInterop] Always consider main-thread layers visible for cc, a=testonly Automatic update from web-platform-tests [TransformInterop] Always consider main-thread layers visible for cc This CL fixes a typo-bug. We should always consider main-thread layers as not "back face visible" because the main thread can't know the final draw transform. This aligns TransformInterop with the equivalent behavior for pre-TransformInterop. Bug: 428458 Change-Id: I4e861262324eadd5b1740ac92bd19391f88061be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2247151 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#779055} -- wpt-commits: 774dc6b89e128d2b95f38c8b191ca10c47df292f wpt-pr: 24159
3b84d46b5df4e8b94c6fd9186a36e464a12c77af: Bug 1644847 [wpt PR 24093] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 17 Jun 2020 01:01:48 +0000 - rev 536813
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1644847 [wpt PR 24093] - Update wpt metadata, a=testonly wpt-pr: 24093 wpt-type: metadata
2ce989e05dbcd551b9620ea54066f9b1bcd511cb: Bug 1644847 [wpt PR 24093] - Avoid memory allocation in AudioWorkletProcessor.process(), a=testonly
Hongchan Choi <hongchan@chromium.org> - Mon, 22 Jun 2020 10:41:15 +0000 - rev 536812
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1644847 [wpt PR 24093] - Avoid memory allocation in AudioWorkletProcessor.process(), a=testonly Automatic update from web-platform-tests Avoid memory allocation in AudioWorkletProcessor.process() Based on the spec [1], the current implementation of AudioWorkletProcessor needs to create a new data container (i.e. WebIDL sequence<>) for input, output, and param arrays. With the new spec change [2], this CL changes the overall design of the audio processing callback: 1. Moves the processing call from AudioWorkletGlobalScope to AudioWorkletProcessor object. 2. AudioWorkletProcessor now keeps the data container within the object and allocate memory when it is needed. The preliminary benchmark shows the sizable improvement in the audio stream quality. The glitch score (= buffer underrun/total callback) is improved by ~9x in the low-tier machine. [3] This is an API change [4], but the real world impact would be negligible because there's no functionality change. [1]: https://webaudio.github.io/web-audio-api/#dom-audioworkletprocessor-process-inputs-outputs-parameters-inputs [2]: https://github.com/WebAudio/web-audio-api/issues/1933#issuecomment-616632754 [3]: https://bugs.chromium.org/p/chromium/issues/detail?id=1086665#c2 [4]: https://chromestatus.com/feature/5647541725036544 Bug: 1071085, 1086665 Change-Id: I3e664754973d4d86649d38c1807c6b9d7830fb96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218702 Reviewed-by: Raymond Toy <rtoy@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#779052} -- wpt-commits: 48a5574b7e1a3d7d952a4b9fe84b049375773e42 wpt-pr: 24093
13f4bcdcf354c384a4a6144c30ee9efa2be93634: Bug 1645756 [wpt PR 24146] - Add manual tests for web manifest, a=testonly
Marcos Cáceres <mcaceres@mozilla.com> - Mon, 22 Jun 2020 10:41:10 +0000 - rev 536811
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645756 [wpt PR 24146] - Add manual tests for web manifest, a=testonly Automatic update from web-platform-tests Add manual tests for web manifest (#24146) -- wpt-commits: 604b85160000869f62832d161751f532bbb38c3c wpt-pr: 24146
7dda7644ffe1336a6035bfcd5392aeee98a86d1e: Bug 1645070 [wpt PR 24109] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 16 Jun 2020 14:57:07 +0000 - rev 536810
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645070 [wpt PR 24109] - Update wpt metadata, a=testonly wpt-pr: 24109 wpt-type: metadata
d5c7bacfde62813c8a4fb2b52669caea8ca50c35: Bug 1645070 [wpt PR 24109] - Parse text-decoration-thickness as part of text-decoration shorthand, a=testonly
Dominik Röttsches <drott@chromium.org> - Mon, 22 Jun 2020 10:41:01 +0000 - rev 536809
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645070 [wpt PR 24109] - Parse text-decoration-thickness as part of text-decoration shorthand, a=testonly Automatic update from web-platform-tests Parse text-decoration-thickness as part of text-decoration shorthand Adapt text-decoration shorthand serialized value to only return non- initial values for text-decoration-thickness according to https://drafts.csswg.org/cssom/#serializing-css-values but keep existing serialisation behavior for other longhands. Shorthand serialisation needs separate harmonisation efforts, see issue 1093826. Bug: 1093827 Change-Id: I391225c383818318c9d22e6c96e3a3c4b9ebb6d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2241677 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#778744} -- wpt-commits: 314d27b572a22e1b341de6fe678768f55791d55a wpt-pr: 24109
b652ecc3478ae04bd6a3f76128b5f5f239fd7853: Bug 1645988 [wpt PR 24165] - Python 3: port tests in document-metadata & embedded-content in html/…, a=testonly
Ziran Sun <zsun@igalia.com> - Mon, 22 Jun 2020 10:40:56 +0000 - rev 536808
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645988 [wpt PR 24165] - Python 3: port tests in document-metadata & embedded-content in html/…, a=testonly Automatic update from web-platform-tests Python 3: port tests in document-metadata & embedded-content in html/semantics -- wpt-commits: aec6139dc296e26757011885238d69c77e17b804 wpt-pr: 24165
4d3d34985ebcd9259fcf1e3323f774d0b079d375: Bug 1646011 [wpt PR 24166] - Correct name of lint.ignore file in docs, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Mon, 22 Jun 2020 10:40:51 +0000 - rev 536807
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646011 [wpt PR 24166] - Correct name of lint.ignore file in docs, a=testonly Automatic update from web-platform-tests Correct name of lint.ignore file in docs (#24166) In https://github.com/web-platform-tests/wpt/pull/24158 the docs were updated, but I got the filename wrong - it's lint.ignore, not lint.ignorelist. -- wpt-commits: 3a3504c07bc32445b91f4df84af95fce9574718d wpt-pr: 24166
95164b155a07497bcb514ed773401744e7df7c8e: Bug 1645966 [wpt PR 24161] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 18 Jun 2020 16:19:09 +0000 - rev 536806
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645966 [wpt PR 24161] - Update wpt metadata, a=testonly wpt-pr: 24161 wpt-type: metadata
81b15d20a74b3209d125d4dd45291f76a8c9e5d2: Bug 1645966 [wpt PR 24161] - RubyNG: A line shouldn't provide annotation space if it has text-emphasis, a=testonly
Kent Tamura <tkent@chromium.org> - Mon, 22 Jun 2020 10:40:43 +0000 - rev 536805
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645966 [wpt PR 24161] - RubyNG: A line shouldn't provide annotation space if it has text-emphasis, a=testonly Automatic update from web-platform-tests RubyNG: A line shouldn't provide annotation space if it has text-emphasis * A line has text-emphasis at the 'under' side, and the next line has ruby at 'over' side, or * A line has ruby at the 'under' side, and the next line has text-emphasis at 'over' side In these two cases, text-emphasis and ruby could be overlapped. This CL fixes this issue. Note: - The legacy ruby also has this issue, but this CL doesn't fix it for the legacy ruby. - The FAIL line in external/wpt/css/css-ruby/line-spacing-expected.txt is expected. We'll fix it soon. Bug: 1069817 Change-Id: Ie2201d577c58a77000c7ace7a1f3de718866a989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2245991 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#778687} -- wpt-commits: bfcaaa8a2261e974b1a162ddd4155984098e90ca wpt-pr: 24161
c372cadf5bd5a89b42154c2a3a7eda5889d687d7: Bug 1645975 [wpt PR 24162] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 16 Jun 2020 11:34:23 +0000 - rev 536804
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645975 [wpt PR 24162] - Update wpt metadata, a=testonly wpt-pr: 24162 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip