db8d4d86141b3ea9d2c41a9911c92c474a0645b5: Bug 1526405 [wpt PR 15173] - Test that the HTMLPortalElement/activate promise is rejected if detached., a=testonly
Jeremy Roman <jbroman@chromium.org> - Tue, 12 Feb 2019 14:08:21 +0000 - rev 459248
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526405 [wpt PR 15173] - Test that the HTMLPortalElement/activate promise is rejected if detached., a=testonly Automatic update from web-platform-tests Test that the HTMLPortalElement/activate promise is rejected if detached. The simplest way to achieve this is to just make a portal and try to activate it straight away. This code was previously unreachable in our tests: https://analysis.chromium.org/p/chromium/coverage/file?host=chromium.googlesource.com&project=chromium/src&ref=refs/heads/master&revision=f3878c07b1c5501e27ea0964d8a0ba0196cf7680&path=//third_party/blink/renderer/core/html/portal/html_portal_element.cc Bug: 916310 Change-Id: I20cc6cbfb242e5466df6ffbbe0e30c065d6806ee Reviewed-on: https://chromium-review.googlesource.com/c/1447030 Reviewed-by: Adithya Srinivasan <adithyas@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#627932} -- wpt-commits: 3e0d3a34b6c854d0c76633d178591fa72c3b780d wpt-pr: 15173
3475e4caac77437f16b92461383d7d312c8de4f9: Bug 1526402 [wpt PR 14866] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 Feb 2019 20:10:16 +0000 - rev 459247
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526402 [wpt PR 14866] - Update wpt metadata, a=testonly wpt-pr: 14866 wpt-type: metadata
a893eccfa409ca96307c64497fb4497f22156f29: Bug 1526402 [wpt PR 14866] - Improve the test names of tests for toJSON behavior., a=testonly
Ms2ger <Ms2ger@gmail.com> - Tue, 12 Feb 2019 14:08:17 +0000 - rev 459246
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526402 [wpt PR 14866] - Improve the test names of tests for toJSON behavior., a=testonly Automatic update from web-platform-tests Improve the test names of tests for toJSON behavior. (#14866) In particular, this avoids duplicate test names when testing with multiple objects (ref #14645). -- wpt-commits: 7fb15bfac1e7380aa74176886120edab9afb5d02 wpt-pr: 14866
3f4a25c12d7d5703f803a0b97bf1a2c756829f3e: Bug 1526399 [wpt PR 15157] - Implement and ship RTCRtpEncodingParameters.scaleResolutionDownBy, a=testonly
Florent Castelli <orphis@chromium.org> - Tue, 12 Feb 2019 14:08:15 +0000 - rev 459245
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526399 [wpt PR 15157] - Implement and ship RTCRtpEncodingParameters.scaleResolutionDownBy, a=testonly Automatic update from web-platform-tests Implement and ship RTCRtpEncodingParameters.scaleResolutionDownBy Intent thread: https://groups.google.com/a/chromium.org/d/msg/blink-dev/SV8evGSU_dw/DIrx9XzvDQAJ Bug: 857048 Change-Id: I32babd443aef05e6f1d062514b27ba5772ab400f Reviewed-on: https://chromium-review.googlesource.com/c/1445934 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#627927} -- wpt-commits: 6865fad535eeb00c6b569ce2b1ee817676236f67 wpt-pr: 15157
a1dd41778d5138b3a77794c3dfc714478a1d4173: Bug 1511278 [wpt PR 14300] - [Azure Pipelines] Run infrastructure/ tests on Windows 10, a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 12 Feb 2019 14:08:13 +0000 - rev 459244
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1511278 [wpt PR 14300] - [Azure Pipelines] Run infrastructure/ tests on Windows 10, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Run infrastructure/ tests on Windows 10 (#14300) This job is only triggered manually until it has been shown to be robust. -- wpt-commits: b5e00132e6843e622cdb952766eb99118b62fddf wpt-pr: 14300
50da34bb368e3ecb6140de7c6b1c2f5a8837b2cb: Bug 1526392 [wpt PR 15180] - Update interfaces/html.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 12 Feb 2019 14:08:10 +0000 - rev 459243
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526392 [wpt PR 15180] - Update interfaces/html.idl, a=testonly Automatic update from web-platform-tests Update interfaces/html.idl (#15180) Source: https://github.com/tidoust/reffy-reports/blob/d1f04f3/whatwg/idl/html.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/486795699 -- wpt-commits: 09c7c724f76a6512d829c20a5b84d0fabba661eb wpt-pr: 15180
67afc906687965677ebed3431f5f87f196dd1eca: Bug 1526388 [wpt PR 15160] - [LayoutNG] Provide both inline resolution sizes to legacy., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Tue, 12 Feb 2019 14:08:08 +0000 - rev 459242
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526388 [wpt PR 15160] - [LayoutNG] Provide both inline resolution sizes to legacy., a=testonly Automatic update from web-platform-tests [LayoutNG] Provide both inline resolution sizes to legacy. When entering legacy layout from NG, we need to provide both percentage resolution inline size and available inline size. Available size is used when using the fill-available measure, i.e. what typically takes place when inline-size is auto. Percentage resolution size is used otherwise (to resolve percentages). We used to provide percentage size if inline-size was percentage based, and available size otherwise. But there are cases where we need both. Any of inline-size, inline-min-size and inline-max-size may or may not be percentage based, and letting the unit type of inline-size decide therefore won't do. Change-Id: I225372584a88471dad35deddbc2d3a7de732583a Reviewed-on: https://chromium-review.googlesource.com/c/1443992 Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#627885} -- wpt-commits: 6b32df28ee471247e7d6e5e1764f1c47ea762f5d wpt-pr: 15160
5eb72f3fdd6a5d8a9f9eb3015af3522b7196fcb2: Bug 1526384 [wpt PR 15078] - HTML: window.open() can set opener of a nested browsing context, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 12 Feb 2019 14:08:06 +0000 - rev 459241
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526384 [wpt PR 15078] - HTML: window.open() can set opener of a nested browsing context, a=testonly Automatic update from web-platform-tests HTML: window.open() can set opener of a nested browsing context Needed for https://github.com/whatwg/html/pull/4284. -- wpt-commits: 5cf7f41336801449ce7499a5f41ccf6848650e9c wpt-pr: 15078
87b23b28d0dc972f3b2f0de6fde7557b3cb1c699: Bug 1526378 [wpt PR 15177] - innerHTML serialization should not have a special handling for javascript: URLs., a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 12 Feb 2019 14:08:04 +0000 - rev 459240
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526378 [wpt PR 15177] - innerHTML serialization should not have a special handling for javascript: URLs., a=testonly Automatic update from web-platform-tests innerHTML serialization should not have a special handling for javascript: URLs. The HTML specification [1] doesn't have such special handling, and Firefox conforms to the specification. Remove fast/innerHTML/javascript-url.html because javascript: URLs are not special any longer. [1] https://html.spec.whatwg.org/multipage/parsing.html#serialising-html-fragments:attribute's-serialised-name Bug: crbug.com/927164 Change-Id: I63317517dc1549190e66f5fdfa44f6bb38545394 Reviewed-on: https://chromium-review.googlesource.com/c/1447164 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#627794} -- wpt-commits: ec735e1c986519995190a1a1089034cb29879914 wpt-pr: 15177
ca2d732a17b44cc2f75bad44b20a9437804d49dc: Bug 1526377 [wpt PR 15164] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 Feb 2019 09:53:35 +0000 - rev 459239
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526377 [wpt PR 15164] - Update wpt metadata, a=testonly wpt-pr: 15164 wpt-type: metadata
391815c7c9ab55affff488a5bb25a5e535024378: Bug 1526377 [wpt PR 15164] - Fixing test to use wpt server features., a=testonly
kdillon <kdillon@chromium.org> - Tue, 12 Feb 2019 14:08:00 +0000 - rev 459238
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526377 [wpt PR 15164] - Fixing test to use wpt server features., a=testonly Automatic update from web-platform-tests Fixing test to use wpt server features. Change-Id: I6c40eacb5635461375543d857b37bb2bd36a2805 Reviewed-on: https://chromium-review.googlesource.com/c/1446773 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#627717} -- wpt-commits: c0d2352f34b33d8cd346b38db301cfa2c5be92f2 wpt-pr: 15164
8452d9d7634b1b7b8509e8db4c4256c95d73a5a3: Bug 1526376 [wpt PR 15151] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 Feb 2019 09:33:33 +0000 - rev 459237
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526376 [wpt PR 15151] - Update wpt metadata, a=testonly wpt-pr: 15151 wpt-type: metadata
5085624b6a31ac148980798f165dae41daad42e9: Bug 1526376 [wpt PR 15151] - [LayoutNG] Fixed elements inside split inlines triggered DCHECK, a=testonly
Aleks Totic <atotic@chromium.org> - Tue, 12 Feb 2019 14:07:55 +0000 - rev 459236
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526376 [wpt PR 15151] - [LayoutNG] Fixed elements inside split inlines triggered DCHECK, a=testonly Automatic update from web-platform-tests [LayoutNG] Fixed elements inside split inlines triggered DCHECK The bug was that position:fixed elements were not getting laid out. It was caused by split inlines containing block fix. I've modified an existing testcase that we used to test split inlines to also test fixed. Bug: 923268 Change-Id: Ic1fe1bbdf1ffc2dfe80e4dbe5c03065be05c082c Reviewed-on: https://chromium-review.googlesource.com/c/1445393 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#627663} -- wpt-commits: ac12b3e9488edb436f063b11213e954ae62d5a5e wpt-pr: 15151
e04fcf3de4cb8e1a269aa8493e8501364de439b3: Bug 1526370 [wpt PR 15170] - [css-font-loading] Handle a fontFace.loaded promise rejection in idlharness test, a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 12 Feb 2019 14:07:47 +0000 - rev 459235
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526370 [wpt PR 15170] - [css-font-loading] Handle a fontFace.loaded promise rejection in idlharness test, a=testonly Automatic update from web-platform-tests [css-font-loading] Handle a fontFace.loaded promise rejection in idlharness test (#15170) Fixes https://github.com/web-platform-tests/wpt/issues/14862. -- wpt-commits: c575a40b789f5c3db95dfe5aa575ce17d02afc74 wpt-pr: 15170
6d02b6175d273dd91d4b85b2e0430645a7c0b7c4: Bug 1526362 [wpt PR 15006] - Plumb the new RRectF rounded rect through to backdrop-filter clip, a=testonly
Mason Freed <masonfreed@chromium.org> - Tue, 12 Feb 2019 14:07:45 +0000 - rev 459234
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526362 [wpt PR 15006] - Plumb the new RRectF rounded rect through to backdrop-filter clip, a=testonly Automatic update from web-platform-tests Plumb the new RRectF rounded rect through to backdrop-filter clip With this CL, the clip rect for backdrop filter also includes rounded corners from the original element. In most cases this works as expected. However, there is still an open bug that causes the rounded corner layout tests to fail. Essentially, if an element has opacity<1 and a single backdrop-filter child, the opacity<1 element does not get a render surface, so the backdrop filter "sees" outside it. I'm fixing that in a separate CL. Bug: 497522,547937 Change-Id: I7f870179193d696d79398fd595c37b293ffbdbde Reviewed-on: https://chromium-review.googlesource.com/c/1415695 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by: enne <enne@chromium.org> Reviewed-by: Dominick Ng <dominickn@chromium.org> Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#627598} -- wpt-commits: 9fa38be81964e0928204db526295f9fee7fa7441 wpt-pr: 15006
9405843fdc4040a2b099602dab91c88f99f8051d: Bug 1526352 [wpt PR 15161] - Click event should not be affected by pointerdown, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Tue, 12 Feb 2019 14:07:43 +0000 - rev 459233
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526352 [wpt PR 15161] - Click event should not be affected by pointerdown, a=testonly Automatic update from web-platform-tests Click event should not be affected by pointerdown As click event is not considered a compatibility mouse event it should not be affected by cancelling pointerdown event and it should be still dispatched in that case. Bug: 926208 Change-Id: I24c54662cf56c73ff92932883040e08b7a2b15ce Reviewed-on: https://chromium-review.googlesource.com/c/1446034 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#627590} -- wpt-commits: 8695aedf2713b9817f970c78e913a7061f870c4f wpt-pr: 15161
e0f03598fadef003a34cca45563fbdbaf4f7c373: Bug 1526346 [wpt PR 15154] - Lock `Sec-Fetch-*` to secure transports., a=testonly
Mike West <mkwst@chromium.org> - Tue, 12 Feb 2019 14:07:41 +0000 - rev 459232
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526346 [wpt PR 15154] - Lock `Sec-Fetch-*` to secure transports., a=testonly Automatic update from web-platform-tests Lock `Sec-Fetch-*` to secure transports. Bug: 926822 Change-Id: I44be594761997ae323c04f2006eaff720019e2eb Reviewed-on: https://chromium-review.googlesource.com/c/1445893 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#627579} -- wpt-commits: 2b8288eaff2633842ef30a5da94320569203c3f4 wpt-pr: 15154
a34f1939a69db74120c0676a16d03dcb0b765923: Bug 1517702 [wpt PR 14711] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 04 Jan 2019 14:40:11 +0000 - rev 459231
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1517702 [wpt PR 14711] - Update wpt metadata, a=testonly wpt-pr: 14711 wpt-type: metadata
8117f527ba5f8dd6f97a2c6c82f55aedd257ff09: Bug 1517702 [wpt PR 14711] - Add CEReactions tests, a=testonly
kaixinjxq <xiuqix.jiang@intel.com> - Tue, 12 Feb 2019 14:07:36 +0000 - rev 459230
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1517702 [wpt PR 14711] - Add CEReactions tests, a=testonly Automatic update from web-platform-tests Add CEReactions tests Part of issue #5727 - HTMLMapElement - HTMLCanvasElement - HTMLDataElement - HTMLDetailsElement - HTMLModElement - HTMLOListElement - HTMLQuoteElement - HTMLSlotElement - HTMLTimeElement -- wpt-commits: 449eccc71de929f5a2f0cec88511e74c06ecfce6 wpt-pr: 14711
452f4020780ab549279975ce7cf955a9a95131ee: Bug 1526341 [wpt PR 15142] - [css-tables] Subpixel tests that Chrome fails but Safari, FF, Edge pass, a=testonly
David Grogan <dgrogan@chromium.org> - Tue, 12 Feb 2019 14:07:34 +0000 - rev 459229
Push 35557 by dvarga@mozilla.com at Fri, 15 Feb 2019 01:42:08 +0000
Bug 1526341 [wpt PR 15142] - [css-tables] Subpixel tests that Chrome fails but Safari, FF, Edge pass, a=testonly Automatic update from web-platform-tests [css-tables] Subpixel tests that Chrome fails but Safari, FF, Edge pass This CL contains tests only, no behavior change. Bug: 377847 Change-Id: I5782e3195094700a9cb992ef2ab9e353ddf048db Reviewed-on: https://chromium-review.googlesource.com/c/1444391 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#627533} -- wpt-commits: 18a1fc0a5f95e08dae436d652c9953f2277dfd8e wpt-pr: 15142
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip