b56e131f6c55b71aaedc1ee25e0a16975194c63c: Bug 1632746 [wpt PR 23221] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 25 Apr 2020 18:39:50 +0000 - rev 527658
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632746 [wpt PR 23221] - Update wpt metadata, a=testonly wpt-pr: 23221 wpt-type: metadata
98fdb2702b013cdab44074adbe973475d6aba18f: Bug 1632746 [wpt PR 23221] - Implement and ship 'ruby-position' CSS property, a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 28 Apr 2020 11:44:37 +0000 - rev 527657
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632746 [wpt PR 23221] - Implement and ship 'ruby-position' CSS property, a=testonly Automatic update from web-platform-tests Implement and ship 'ruby-position' CSS property This CL implements 'ruby-position' CSS property, which is a property independent from the existing '-webkit-ruby-position', but these properties share a single ComputedStyle field. We apply neither legacy name alias [1] nor legacy shorthands [2] because - Acceptable keyword sets are different in ruby-position and -webkit-ruby-position. - Avoid behavior changes with |element.style.webkitRubyPosition = 'after'|. * core/css/css_computed_style_declaration.cc Add 'ruby-position' to getComputedStyle() enumeration. * core/css/parser/css_parser_fast_paths.cc Add setting for fast-path parsing * core/css/properties/longhands/longhands_custom.cc Add CSSValueFromComputedStyleInternal() to translate a ComputedStyle:: GetRubyPosition() value to 'over' or 'under'. * core/css/resolver/style_builder_converter.{h,cc} Add a function to convert a parsed CSS keyword to a blink::RubyPosition value. * web_tests/external/wpt/css/css-ruby/ruby-position.html New test to check ruby annotation position. * web_tests/fast/ruby/ruby-position-om.html New test to check relationship between ruby-position and -webkit-ruby-position. Approved intent: https://t.co/nmCPv0Onhk [1] https://drafts.csswg.org/css-cascade/#legacy-name-alias [2] https://drafts.csswg.org/css-cascade/#legacy-shorthand Bug: 196690 Change-Id: I2f00099f90a2222b7ddba8b58c3a532f3b997744 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152569 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#762664} -- wpt-commits: ae457cd8b39790508e841f581e2066871859db1a wpt-pr: 23221
b385b9e049d31a78e7016c0f2e4fbe1048ffa832: Bug 1632681 [wpt PR 23218] - Update Safari Technology Preview to 105, a=testonly
autofoolip <auto@foolip.org> - Tue, 28 Apr 2020 11:44:32 +0000 - rev 527656
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632681 [wpt PR 23218] - Update Safari Technology Preview to 105, a=testonly Automatic update from web-platform-tests Update Safari Technology Preview to 105 (#23218) Version as reported by safaridriver --version: Included with Safari Technology Preview (Release 105, 15610.1.10) Source: https://developer.apple.com/safari/download/ Build: https://dev.azure.com/foolip/safari-technology-preview-updater/_build/results?buildId=1718&view=logs -- wpt-commits: 63f66e28a46d7ba84013a9d9082f3337be30abb3 wpt-pr: 23218
21f3e5c1d6d202723332cdf0d872238d275bbb1b: Bug 1632988 [wpt PR 23240] - Update two SVG tests to be consistent between browsers, a=testonly
Myles C. Maxfield <litherum@icloud.com> - Tue, 28 Apr 2020 11:44:27 +0000 - rev 527655
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632988 [wpt PR 23240] - Update two SVG tests to be consistent between browsers, a=testonly Automatic update from web-platform-tests Update two SVG tests to be consistent between browsers (#23240) svg/import/pservers-grad-08-b-manual.svg: This test renders some text using a font that doesn't contain the space glyph. However, the content contains the space character, and doesn't specify a fallback font. This means that different browsers on the same OS will pick different fallback fonts, causing different renderings. Instead, the test should be updated to specify a fallback font, which makes browsers render it consistently. imported/w3c/web-platform-tests/svg/import/text-altglyph-01-b-manual.svg: Similarly, this test renders text with a font that doesn't support those characters. (It does it using <altGlyph>, but support for <altGlyph> has been removed in SVG 2.0 and neither Safari nor Firefox support it.) A fallback font should be supplied to the test to get consistent renderings across browsers. Co-authored-by: Myles C. Maxfield <mmaxfield@apple.com> -- wpt-commits: 51151cf5bfc32adb8d96fca51a30c126d1e0200d wpt-pr: 23240
d700bf57b90b613f5dee497a4a7f6a3c2d665476: Bug 1633059 [wpt PR 23245] - Replace assert_precondition in workers/, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:44:13 +0000 - rev 527654
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1633059 [wpt PR 23245] - Replace assert_precondition in workers/, a=testonly Automatic update from web-platform-tests Replace assert_precondition in workers/ assert_precondition is deprecated (see https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md). -- wpt-commits: 78eae724c61bb01d858a01a324363e997ac66851 wpt-pr: 23245
4ef42579cac5b2ee7ffedecb46b89f57f89cd0f1: Bug 1631973 [wpt PR 23157] - bluetooth: Split bluetooth-helpers.js, a=testonly
Ovidio Henriquez <odejesush@chromium.org> - Tue, 28 Apr 2020 11:44:08 +0000 - rev 527653
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631973 [wpt PR 23157] - bluetooth: Split bluetooth-helpers.js, a=testonly Automatic update from web-platform-tests bluetooth: Split bluetooth-helpers.js This change splits the bluetooth-helpers.js files in two. The new bluetooth-test.js file contains methods for setting up the web tests and for asserting conditions. The bluetooth-helpers.js file now contains helper methods that set up fake Bluetooth devices for use in the Web Bluetooth tests. I added JsDoc style comments to the helper methods to make it clear what kinds of objects are expected as parameters and what the methods will return. I also reordered the bluetooth-helpers.js methods so that they are defined before they are used. Bug: 1070816 Change-Id: Ib5215555be2b24b11f8dea9098d83ad69719a284 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149909 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: James Hollyer <jameshollyer@google.com> Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#762594} -- wpt-commits: 6f8f0b30a4af91762427b4ff528ed344d5636c6d wpt-pr: 23157
974b68ffab59f2e9e3b2c677399e1f8054440486: Bug 1631939 [wpt PR 23152] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 25 Apr 2020 02:02:36 +0000 - rev 527652
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631939 [wpt PR 23152] - Update wpt metadata, a=testonly wpt-pr: 23152 wpt-type: metadata
a3d9580e4b6f9d62baa7fa8325b6609b3763eca1: Bug 1631939 [wpt PR 23152] - [EventTiming] Implement durationThreshold, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Tue, 28 Apr 2020 11:44:00 +0000 - rev 527651
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631939 [wpt PR 23152] - [EventTiming] Implement durationThreshold, a=testonly Automatic update from web-platform-tests [EventTiming] Implement durationThreshold This CL implements a durationThreshold member of PerformanceObserverInit which enables setting a threshold for the event timing entries received by a PerformanceObserver. The entries are still buffered per the default duration threshold of 104 for now. Tests are added for various threshold values. PR: https://github.com/WICG/event-timing/pull/82 Bug: 543598 Change-Id: Id3407ddbcd1713fc33036518bbf88696add423cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159611 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#762168} -- wpt-commits: c7f5f1561f751232d7577d21808e45af289a2d46 wpt-pr: 23152
073c2315b5d8923c57f1c4a55dc55f654857d365: Bug 1632883 [wpt PR 23233] - Be responsive to reference box changes for transformed containers, a=testonly
Fredrik Söderqvist <fs@opera.com> - Tue, 28 Apr 2020 11:43:55 +0000 - rev 527650
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632883 [wpt PR 23233] - Be responsive to reference box changes for transformed containers, a=testonly Automatic update from web-platform-tests Be responsive to reference box changes for transformed containers This adapts the technique used elsewhere to work with LayoutSVGContainers (specifically LayoutSVGTransformableContainer). Bug: 697052, 1074080 Change-Id: I5dc1ca440aaa2d76eb49ae54fb0c4422f166c4f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165107 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#762562} -- wpt-commits: 15f0671b0ebffbe0d7fd64fdbdb4f2e69fb0eb3e wpt-pr: 23233
1e888d39e6a8b02b2fc5373c4cdb5e3bf33359ae: Bug 1632885 [wpt PR 23234] - Account for root element paint offset when painting backgrounds, a=testonly
Philip Rogers <pdr@chromium.org> - Tue, 28 Apr 2020 11:43:50 +0000 - rev 527649
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632885 [wpt PR 23234] - Account for root element paint offset when painting backgrounds, a=testonly Automatic update from web-platform-tests Account for root element paint offset when painting backgrounds The root background is painted from the coordinate space of the root element, but expands to fill the viewport. The difference between these spaces needs to be used as an offset when painting the background. For the non-transform case, this patch removes the paint offset adjustment made to the entire paint rect in ViewPainter, and only applies the paint offset for positioning the background in BackgroundImageGeometry::ComputePositioningArea. This way, painting starts from the origin, without paint offset. For the transform case, paint properties will apply the paint offset, and the entire paint rect needs to be adjusted to remove the paint offset. This patch specifies the transform state of the view and root element, and uses GeometryMapper to map the background paint rect into the coordinate space of the root element. A TODO has been added to more clearly specify the non-transform and transform cases. Bug: 1071957 Change-Id: Iedc1834ef9c400340b668b3eec73a0f3f4506194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161350 Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#762543} -- wpt-commits: f8bd87deb2c2a0ea974adb6c64ef013a60188193 wpt-pr: 23234
27adb5f3a59d71cb81c05fe2643648fa00cd2d2f: Bug 1632882 [wpt PR 23232] - [ua-ch] s/uaList/brands/, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Tue, 28 Apr 2020 11:43:45 +0000 - rev 527648
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632882 [wpt PR 23232] - [ua-ch] s/uaList/brands/, a=testonly Automatic update from web-platform-tests [ua-ch] s/uaList/brands/ This aligns the UA-CH implementation with [1] [1] https://github.com/WICG/ua-client-hints/pull/99 Change-Id: I903450f3103c7068aa7548b69b986593d13d8904 Bug: 1074338 Change-Id: I903450f3103c7068aa7548b69b986593d13d8904 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2164526 Reviewed-by: Aaron Tagliaboschi <aarontag@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762448} -- wpt-commits: c0129ead75677b772594d7c41b9da836ecaf5019 wpt-pr: 23232
cbd6f7704725938468343263cc2a20a2b9db79d5: Bug 1632703 [wpt PR 23220] - Create LayoutShiftAttribution objects in LayoutShiftTracker., a=testonly
Steve Kobes <skobes@chromium.org> - Tue, 28 Apr 2020 11:43:40 +0000 - rev 527647
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632703 [wpt PR 23220] - Create LayoutShiftAttribution objects in LayoutShiftTracker., a=testonly Automatic update from web-platform-tests Create LayoutShiftAttribution objects in LayoutShiftTracker. Also mark the REF "experimental", so that it is tested, and add a test. Bug: 1053510 Change-Id: I8bac9c8002d20991599a1bf396f28dd9101b0f63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157988 Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#762442} -- wpt-commits: a7b88cb7b8ba75a5399aee54540f03bb88924672 wpt-pr: 23220
f2f8da81f9bbe819826850a08815391c690bd652: Bug 1632608 [wpt PR 23211] - WPT Chromium logger bug fixes to integrate with results viewer., a=testonly
Luke Zielinski <lpz@chromium.org> - Tue, 28 Apr 2020 11:43:35 +0000 - rev 527646
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632608 [wpt PR 23211] - WPT Chromium logger bug fixes to integrate with results viewer., a=testonly Automatic update from web-platform-tests WPT Chromium logger bug fixes to integrate with results viewer. Three main issues fixed here: 1. Removing a trailing whitespace in the "expected" field. This is caused by "known_intermittent" always being present in the test_end data dict, but simply being empty when no intermittent statuses exist. 2. Making sure the start timestamp is always in seconds - the wpt test framework provides it in microseconds, but we can fallback to "now" which returns seconds. 3. All artifacts are expected to be lists. Bug: 1070265 Change-Id: I3dc98f8e37d847727c3165ab51c293f529d3c5eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163065 Commit-Queue: Robert Ma <robertma@chromium.org> Auto-Submit: Luke Z <lpz@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#762415} -- wpt-commits: 01aed092cae7983b2d4ecf29097e33ce4e9af5b9 wpt-pr: 23211
7e01a08f71484cde80fdbae58df7d84865f44b8a: Bug 1632905 [wpt PR 23235] - [client hints] Add WPTs for subresource redirects, a=testonly
Aaron Tagliaboschi <aarontag@chromium.org> - Tue, 28 Apr 2020 11:43:25 +0000 - rev 527645
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632905 [wpt PR 23235] - [client hints] Add WPTs for subresource redirects, a=testonly Automatic update from web-platform-tests [client hints] Add WPTs for subresource redirects Making sure subresource *don't* register client hint preferences on redirects. Bug: 1042828 Change-Id: I050e81e9473ce7c771763d9b18fc2e1843ab5546 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154849 Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762401} -- wpt-commits: 39e9c51041a1be64b61281ddc2381ffe33d05b84 wpt-pr: 23235
120e8aff42180089d1e93917dd21d777ed1e624e: Bug 1632819 [wpt PR 23228] - Update interfaces/webrtc-stats.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 28 Apr 2020 11:43:20 +0000 - rev 527644
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632819 [wpt PR 23228] - Update interfaces/webrtc-stats.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webrtc-stats.idl (#23228) Source: https://github.com/tidoust/reffy-reports/blob/eeef44a/ed/idl/webrtc-stats.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/679007987 -- wpt-commits: c430c87d74939e9a10fbf00782fa49669ec0bd5b wpt-pr: 23228
a5f6c82150a89c4102d46840b7e254ea6d8f80a7: Bug 1632816 [wpt PR 23227] - Mark clipboard-apis/async-idlharness.https.html as timeout=long, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:43:08 +0000 - rev 527643
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632816 [wpt PR 23227] - Mark clipboard-apis/async-idlharness.https.html as timeout=long, a=testonly Automatic update from web-platform-tests Mark clipboard-apis/async-idlharness.https.html as timeout=long This is symptomatic of crbug.com/1047818, but to stop the pain for sheriffs lets mark it timeout=long for now. Bug: 1073055 Change-Id: I1e17f6a0fe2dc66f4c842b80361057cb19a3edc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163955 Reviewed-by: Luke Z <lpz@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#762348} -- wpt-commits: a6396b8566a7a85fa2ce33abfc480cc7e48574aa wpt-pr: 23227
8a97b14a89da6eaca9dc3914cc6331d7c883f2da: Bug 1621081 [wpt PR 22145] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 15:39:26 +0000 - rev 527642
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1621081 [wpt PR 22145] - Update wpt metadata, a=testonly wpt-pr: 22145 wpt-type: metadata
06bb3722f5d3a0ef36a5a5ecbf87b15629327527: Bug 1621081 [wpt PR 22145] - Use assert_implements in test the-input-element/type-change-state.html, a=testonly
Carlos Alberto Lopez Perez <clopez@igalia.com> - Tue, 28 Apr 2020 11:43:00 +0000 - rev 527641
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1621081 [wpt PR 22145] - Use assert_implements in test the-input-element/type-change-state.html, a=testonly Automatic update from web-platform-tests Use assert_implements in test the-input-element/type-change-state.html (#22145) * Use assert_implements to check if the browser supports both input element types before trying to change the state from one to other. * For example, WebKitGTK and Safari doesn't support several of the input types tested here (like those related to dates). The output of the test its clearer if the precondition its checked before. -- wpt-commits: af8fb743e877884ae9f6cec97a60da6e22d06740 wpt-pr: 22145
883dc067324332f1312db2498ac52a73d309887c: Bug 1619698 [wpt PR 22068] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 14:44:35 +0000 - rev 527640
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1619698 [wpt PR 22068] - Update wpt metadata, a=testonly wpt-pr: 22068 wpt-type: metadata
5660496a4c1aa1360905a20055248051cde18159: Bug 1619698 [wpt PR 22068] - [client hints] Fix handling of redirects in navigation, a=testonly
Maks Orlovich <morlovich@chromium.org> - Tue, 28 Apr 2020 11:42:52 +0000 - rev 527639
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1619698 [wpt PR 22068] - [client hints] Fix handling of redirects in navigation, a=testonly Automatic update from web-platform-tests [client hints] Fix handling of redirects in navigation In particular, the browser needs to handle accept-ch there since the renderer doesn't see the intermediate steps until after everything is fetched, and new client hints may be requested in the middle of the chain. This is done by having the network service parse the header and store in ParseHeaders, then using that in the browser This is also likely the first step towards moving more of handling of accept-ch to browser (which will simplify some things and fix some bugs). Bug: 1050726 Change-Id: Ie02d7492c02b75034b36af30e489ebbb430d6a1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2085114 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762329} -- wpt-commits: 39411b7ef888f9bd67e430970042f757bac0bed0 wpt-pr: 22068
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip