c494ab0b6fab0dd339b7ca6fc13c36ad56e19568: Bug 1632580 [wpt PR 23207] - Update interfaces/fullscreen.idl, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:45:38 +0000 - rev 527667
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632580 [wpt PR 23207] - Update interfaces/fullscreen.idl, a=testonly Automatic update from web-platform-tests Update interfaces/fullscreen.idl (#23207) Includes necessary idlharness.js updates for https://github.com/web-platform-tests/wpt/issues/23148 Closes https://github.com/web-platform-tests/wpt/pull/23128 -- wpt-commits: 7b4b5b84caae9e748eb13fda010d48a6a874e5a4 wpt-pr: 23207
0f3c24ba4e85c00ead3a93cea27749ee364e9eb7: Bug 1632773 [wpt PR 23222] - FindKeyframesRules should use originating element., a=testonly
Rune Lillesveen <futhark@chromium.org> - Tue, 28 Apr 2020 11:45:33 +0000 - rev 527666
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632773 [wpt PR 23222] - FindKeyframesRules should use originating element., a=testonly Automatic update from web-platform-tests FindKeyframesRules should use originating element. It's only using the TreeScope to find @keyframes in which case using the originating element for pseudo elements should work. Even better when the originating element is a shadow host, so that we look up :host rules from the shadow tree for :host::before { animation-name: anim }. Bug: 961941 Change-Id: I38edec156eaaa7cfb3680762b135323deae00a68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2162988 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#762791} -- wpt-commits: 245ed57a5e400fff2dc4adbf8e452d64397399cd wpt-pr: 23222
117465eac2d79362fa60f0f82850fe11cb76986e: Bug 1631842 [wpt PR 23144] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 27 Apr 2020 11:51:40 +0000 - rev 527665
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631842 [wpt PR 23144] - Update wpt metadata, a=testonly wpt-pr: 23144 wpt-type: metadata
1ec9b02985ce186ba668be2ab21ae351da1356a0: Bug 1631842 [wpt PR 23144] - Forward CSP, even for the initial empty document., a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Tue, 28 Apr 2020 11:45:25 +0000 - rev 527664
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631842 [wpt PR 23144] - Forward CSP, even for the initial empty document., a=testonly Automatic update from web-platform-tests Forward CSP, even for the initial empty document. Bug 1064676 has been fixed by: https://chromium-review.googlesource.com/c/chromium/src/+/2111170 And tested by: https://chromium-review.googlesource.com/c/chromium/src/+/2144012 The bug was fixed for every CSP checked in the renderer process. However there are still an issue for the one checked in the browser process. It turns out the CSP in the initial empty document weren't properly propagated to the browser process. This patch: 1) Fix the bug by sending the CSP of the initial empty document. 2) Add a regression test (WPT). This patch can potentially also fix: - https://crbug.com/1072719 - https://crbug.com/955350 (I haven't checked. I will do it later after landing this patch) Bug: 1064676, 1072719, 955350 Change-Id: Ie5325035c74d9e2476d6c80af3e5d5c9068ea928 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159242 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#762769} -- wpt-commits: 7179786e28b8266789355518b65b8df65aa962c2 wpt-pr: 23144
0cb8ec84d28fdb7002912419e301c0c3a6e5d50c: Bug 1632222 [wpt PR 23174] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 27 Apr 2020 03:42:37 +0000 - rev 527663
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632222 [wpt PR 23174] - Update wpt metadata, a=testonly wpt-pr: 23174 wpt-type: metadata
cad85ca01c012cb1eeb6b1517f3ea0c6f18c5e5a: Bug 1632222 [wpt PR 23174] - Migrate pointerevents/mouse-on-object.html to wpt, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Tue, 28 Apr 2020 11:45:07 +0000 - rev 527662
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632222 [wpt PR 23174] - Migrate pointerevents/mouse-on-object.html to wpt, a=testonly Automatic update from web-platform-tests Migrate pointerevents/mouse-on-object.html to wpt The expected behavior on this test seems to be a hack as it implicitly captures mouse to the object and still sends the mouseup/pointerup to the object when down happened on the object even though up is happening outside of the object. This seems to resolving compat issues on embedded flash objects. Change-Id: Ibd888a989dbcf5e6ff08b35569903967edc957e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160142 Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#762476} -- wpt-commits: 55367a4c706fa32301980773cb2c09cbcd291635 wpt-pr: 23174
c4e45af3abbd1350c337ec56a0b9835c0b0697fd: Bug 1633228 [wpt PR 23254] - Fix mobile table, a=testonly
Anthony Frehner <afrehner.work@gmail.com> - Tue, 28 Apr 2020 11:45:02 +0000 - rev 527661
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1633228 [wpt PR 23254] - Fix mobile table, a=testonly Automatic update from web-platform-tests for larger tables on mobile, you have to wrap in a div and set overflow to auto so that they'll scroll the div instead of the window -- wpt-commits: 5e7cbed423a3040dc8ca50359dd033a46dba5cf4 wpt-pr: 23254
22e877bcc6c34ad21bb4b575d76f96772249d6dd: Bug 1631314 [wpt PR 23100] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 26 Apr 2020 04:19:14 +0000 - rev 527660
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631314 [wpt PR 23100] - Update wpt metadata, a=testonly wpt-pr: 23100 wpt-type: metadata
e7b48c4763c6aae2ca6d835bbb27cf7722ea4108: Bug 1631314 [wpt PR 23100] - [device-orientation] Simplifies tests by using EventWatcher, a=testonly
Wanming Lin <wanming.lin@intel.com> - Tue, 28 Apr 2020 11:44:45 +0000 - rev 527659
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631314 [wpt PR 23100] - [device-orientation] Simplifies tests by using EventWatcher, a=testonly Automatic update from web-platform-tests [device-orientation] Simplifies tests by using EventWatcher This CL simplifies wpt/orientation-event tests by using testharness.js' `EventWatcher` to replace existing customized `waitForEvent` method and improving event comparison methods. Uses `setGetSensorShouldFail` to simulate UA can not provide sensor information for orientation/deviceorientationabsoluteevent.https.html, and merges which into orientation/basic-operation-absolute.https.html. Bug: 816462 Change-Id: Ia7bf83cb9401265722e472ccdd01adc114eff660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154389 Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#762675} -- wpt-commits: 44915d53e1747700990f4f03442040e59cd2da19 wpt-pr: 23100
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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip