91d1ee513a26355e49e8379c425dc833beeffcdc: Bug 1668565 - Update help for --setpref in Marionette r=marionette-reviewers,whimboo
Ted Campbell <tcampbell@mozilla.com> - Fri, 02 Oct 2020 07:52:52 +0000 - rev 551286
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1668565 - Update help for --setpref in Marionette r=marionette-reviewers,whimboo Differential Revision: https://phabricator.services.mozilla.com/D92070
5d305d85f70c32d050cb01ac90f06a7d465ac28a: Bug 1668565 - Update help for --setpref in Raptor/talos r=perftest-reviewers,sparky
Ted Campbell <tcampbell@mozilla.com> - Fri, 02 Oct 2020 13:42:33 +0000 - rev 551285
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1668565 - Update help for --setpref in Raptor/talos r=perftest-reviewers,sparky Differential Revision: https://phabricator.services.mozilla.com/D92069
4c92b9d3c7d8d58ef42148232edde5c30149f61e: Bug 1551615 - Have GeckoMediaPluginServiceChild use async shutdown blocker. r=jbauman
Bryce Van Dyk <bvandyk@mozilla.com> - Fri, 02 Oct 2020 13:32:41 +0000 - rev 551284
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1551615 - Have GeckoMediaPluginServiceChild use async shutdown blocker. r=jbauman Differential Revision: https://phabricator.services.mozilla.com/D75180
151d4618b8ea31a972713e51817d48e75645e8c7: Bug 1551615 - Make PGMPService protocol refcounted. r=nika
Bryce Seager van Dyk <bvandyk@mozilla.com> - Fri, 02 Oct 2020 13:32:10 +0000 - rev 551283
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1551615 - Make PGMPService protocol refcounted. r=nika Differential Revision: https://phabricator.services.mozilla.com/D75178
34e6bd2c67db5c52c671fa84414ad37b238c2d94: Bug 1551615 - Make PGMPContent protocol refcounted. r=nika
Bryce Seager van Dyk <bvandyk@mozilla.com> - Fri, 02 Oct 2020 13:31:40 +0000 - rev 551282
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1551615 - Make PGMPContent protocol refcounted. r=nika Differential Revision: https://phabricator.services.mozilla.com/D68904
88ea67980c3a8b0cb73826835ca77bfea18fb47d: Bug 1666219 - Renamed QM_TRY_VAR etc. to QM_TRY_UNWRAP etc. r=dom-workers-and-storage-reviewers,ttung,janv
Simon Giesecke <sgiesecke@mozilla.com> - Fri, 02 Oct 2020 13:23:49 +0000 - rev 551281
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1666219 - Renamed QM_TRY_VAR etc. to QM_TRY_UNWRAP etc. r=dom-workers-and-storage-reviewers,ttung,janv Also change some left-over QM_TRY_VAR uses with const target declarations to QM_TRY_INSPECT et al. Differential Revision: https://phabricator.services.mozilla.com/D90873
f93a829f7f1271f2327bc6947fe8db934f3dd3cc: Bug 1609381 - arm64 baseline simd, part 3: masm support. r=jseward
Lars T Hansen <lhansen@mozilla.com> - Fri, 02 Oct 2020 13:09:12 +0000 - rev 551280
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1609381 - arm64 baseline simd, part 3: masm support. r=jseward Add porting interfaces for arm64 and adapt the baseline compiler to use them. Differential Revision: https://phabricator.services.mozilla.com/D90743
c5c66994bd790503b396f1bde79efce88dcfca26: Bug 1609381 - arm64 baseline simd, part 2: sundry cleanup. r=jseward
Lars T Hansen <lhansen@mozilla.com> - Fri, 02 Oct 2020 13:13:07 +0000 - rev 551279
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1609381 - arm64 baseline simd, part 2: sundry cleanup. r=jseward Various cleanup: - significantly simplify SIMD emitters in the baseline compiler: we don't need to have various emitters with names like ...WithTemp and ...WithTwoTemps, it is enough to use the base name of the operation and rely on overloading. This in turn leads to opportunities for templates, which are introduced systematically here, leading to the removal of many special-case emitters. - remove some dead SIMD code in the masm - rename a misnamed API (the SIMD averages are unsigned averages) - rename some mismatched parameter names Differential Revision: https://phabricator.services.mozilla.com/D90742
7f28798f0762577356c3fbb897ee3b8c6c326c62: Bug 1609381 - arm64 baseline simd, part 1: config, register sets, stubs. r=jseward
Lars T Hansen <lhansen@mozilla.com> - Fri, 02 Oct 2020 13:12:42 +0000 - rev 551278
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1609381 - arm64 baseline simd, part 1: config, register sets, stubs. r=jseward This lays the groundwork for ARM64 simd in the baseline compiler and runtime. Mostly this is non-dramatic. The main problem to be solved is SIMD register allocation and save/restore in the stubs. We can't use the register sets in the usual way to do this for reasons that are explained at length in comments in Architecture-arm64.h, WasmStubs.cpp, and WasmBaselineCompile.cpp, so there are a couple of cheats, that basically come down to (sometimes contextually) treating doubles as vectors. By and large this is surprisingly clean. The patch also splits a huge test file (simd/spec/nan-flavors.js) into many smaller files so as to avoid OOM conditions when testing on device with --ion-eager and similar switch settings that cause massive amounts of jit code to be allocated. Differential Revision: https://phabricator.services.mozilla.com/D90740
c028d53c18c7e3503e90b23f4636e46505c0a4b3: Bug 1666747 - Check for partial writes with partial-OOB stores. r=rhunt
Lars T Hansen <lhansen@mozilla.com> - Fri, 02 Oct 2020 13:12:14 +0000 - rev 551277
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1666747 - Check for partial writes with partial-OOB stores. r=rhunt Factor existing partial-OOB-store checks out of the SIMD tests into a separate file. Add non-SIMD partial-OOB-store tests in a separate file. Disable these tests for ARM and ARM64 because we don't handle that correctly on all devices yet. Differential Revision: https://phabricator.services.mozilla.com/D91415
eb9fbdec50a13c43e4c10dca4e0b344fe3bbf3a2: Backed out changeset a3cbffeb24a3 (bug 1668577) for perma failures on location_reload.html. CLOSED TREE
Razvan Maries <rmaries@mozilla.com> - Fri, 02 Oct 2020 19:11:53 +0300 - rev 551276
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Backed out changeset a3cbffeb24a3 (bug 1668577) for perma failures on location_reload.html. CLOSED TREE
1ac1579b1471067fdeb105b8f1fed563326f5451: Backed out changeset 20fadec3e9dc (bug 1187682) for perma failures on layout/reftests/mathml/stretchy-munderover-1c.html. CLOSED TREE
Razvan Maries <rmaries@mozilla.com> - Fri, 02 Oct 2020 17:11:33 +0300 - rev 551275
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Backed out changeset 20fadec3e9dc (bug 1187682) for perma failures on layout/reftests/mathml/stretchy-munderover-1c.html. CLOSED TREE
62112d7e4fd9e6931ca7c246ef6ef3c4d1dd4727: Bug 1668392 - [wpt-sync] Update web-platform-tests to 2531feaeef0530450b7a7271b2bb4cc450edb831, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 30 Sep 2020 22:07:54 +0000 - rev 551274
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1668392 - [wpt-sync] Update web-platform-tests to 2531feaeef0530450b7a7271b2bb4cc450edb831, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 2531feaeef0530450b7a7271b2bb4cc450edb831 wpt-type: landing
339856f276287301bfc852c8ddfe561a6ff1d986: Bug 1667626 [wpt PR 25805] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 28 Sep 2020 18:25:03 +0000 - rev 551273
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667626 [wpt PR 25805] - Update wpt metadata, a=testonly wpt-pr: 25805 wpt-type: metadata
eba41c8e77baea1f040467c83658f388e56e5f2d: Bug 1667626 [wpt PR 25805] - [css-flex] Pass a ConstraintSpace to ortho_table.ComputeMinMaxSizes(), a=testonly
David Grogan <dgrogan@chromium.org> - Wed, 30 Sep 2020 22:07:39 +0000 - rev 551272
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667626 [wpt PR 25805] - [css-flex] Pass a ConstraintSpace to ortho_table.ComputeMinMaxSizes(), a=testonly Automatic update from web-platform-tests [css-flex] Pass a ConstraintSpace to ortho_table.ComputeMinMaxSizes() ComputeMinMaxSizes needs a ConstraintSpace when the child is not in a parallel writing mode. Flex wasn't providing one when it retrieved a table's intrinsic min size. Before this bug was introduced, flex was calling ComputeMinAndMaxContentContribution(..., table, ...) instead of table.ComputeMinMaxSizes(...). ComputeMinAndMaxContentContribution builds its own ConstraintSpace for ortho items, so flex didn't need to provide one. We originally switched from ComputeMinAndMaxContentContribution to table.ComputeMinMaxSizes because: * One input to the flex algorithm is the item's used min-width (for a row flexbox). The flex algorithm will never assign a flex item a width smaller than its used min-width. For most elements, we get this value via ResolveMinInlineLength(..., style.LogicalMinWidth(), ...). * But table's used min-width is defined specially to be "the greater of the resolved min-width, CAPMIN, and GRIDMIN". So to get the table-as-flex-item's used min-width, we need to retrieve max(CAPMIN, GRIDMIN) in addition to resolving style.LogicalMinWidth from the above step. * ComputeMinAndMaxContentContribution(table).min returns max(CAPMIN, GRIDMIN, style.LogicalWidth()). I.e. it obeys any specified width on the table. * But table.ComputeMinMaxSizes().min returns only max(CAPMIN, GRIDMIN)[1], which is what we want. In the example below, the flexbox will try to shrink the table's width to 75px. Using ComputeMinAndMaxContentContribution for the table's min-width computation would result in the table being 100px wide. Using table.ComputeMinMaxSizes would make it 75px wide. 75px is correct. <div style="display: flex; width: 75px;"> <table style="width: 100px; min-width: 0px;"> <td> <div style="float: left; width:50px"></div> <div style="float: left; width:50px"></div> </td> </table> </div> https://jsfiddle.net/dgrogan/gwu4ac82/3/ [1] This is actually not true today but is true for TablesNG. Switching to table.ComputeMinMaxSizes gets us closer. Bug: 1128262 Fixed: 1131890 Change-Id: Ie5a4eac97e4a6a2e96104397bd5c5ec483d40e78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433594 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#811216} -- wpt-commits: 2531feaeef0530450b7a7271b2bb4cc450edb831 wpt-pr: 25805
9e1ac00b7bb147d2b46d2d8f8e0c8ddeba164a38: Bug 1667773 [wpt PR 25811] - Increase timeout of Content-Security-Policy WP test, a=testonly
Antonio Sartori <antoniosartori@chromium.org> - Wed, 30 Sep 2020 22:07:36 +0000 - rev 551271
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667773 [wpt PR 25811] - Increase timeout of Content-Security-Policy WP test, a=testonly Automatic update from web-platform-tests Increase timeout of Content-Security-Policy WP test The WP test content-security-policy/embedded-enforcement/required_csp-header-crlf.html has been marked as flaky lately on Mac because it was incurring in the timeout (see https://crbug.com/1091896). Since the test opens and navigates several iframes, this is understandable, so let's increase the timeout. Bug: 1091896 Change-Id: Ibdc05589eed0188a4782f45693963aa15cfb671a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435347 Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#811199} -- wpt-commits: df557c6e8643150676ce4d4a3c5145dbd0c1ecf0 wpt-pr: 25811
3a0ddadf5bddfed7191ed0ea32c77eeb458e20e5: Bug 1667107 [wpt PR 25774] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 28 Sep 2020 10:03:59 +0000 - rev 551270
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667107 [wpt PR 25774] - Update wpt metadata, a=testonly wpt-pr: 25774 wpt-type: metadata
1fbac28e8bfae08014b7524347709819af880c64: Bug 1667107 [wpt PR 25774] - Add interfaces/webrtc-insertable-streams.idl and test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 30 Sep 2020 22:07:28 +0000 - rev 551269
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667107 [wpt PR 25774] - Add interfaces/webrtc-insertable-streams.idl and test, a=testonly Automatic update from web-platform-tests Add interfaces/webrtc-insertable-streams.idl and test (#25774) Closes https://github.com/web-platform-tests/wpt/pull/25766 -- wpt-commits: b1d0f5495d39d36b7853d0c53a9fd096abba226d wpt-pr: 25774
60784d9ddd97c59190a05c793869d2227b8d2145: Bug 1667083 [wpt PR 25769] - Rename text-detection-api.tentative.idl to text-detection-api.idl, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 30 Sep 2020 22:07:24 +0000 - rev 551268
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667083 [wpt PR 25769] - Rename text-detection-api.tentative.idl to text-detection-api.idl, a=testonly Automatic update from web-platform-tests Rename text-detection-api.tentative.idl to text-detection-api.idl (#25769) Closes https://github.com/web-platform-tests/wpt/pull/25753 -- wpt-commits: 14d4862beeb02904dc6712d62a36c04474bacf12 wpt-pr: 25769
d96bfb74e3975cca3d62c762444594c9adcbf598: Bug 1667452 [wpt PR 25795] - Reset trailing space structure when rewinding due to overflow handling, a=testonly
Javier Fernández García-Boente <jfernandez@igalia.com> - Wed, 30 Sep 2020 22:07:21 +0000 - rev 551267
Push 37830 by nbeleuzu@mozilla.com at Sat, 03 Oct 2020 10:23:35 +0000
Bug 1667452 [wpt PR 25795] - Reset trailing space structure when rewinding due to overflow handling, a=testonly Automatic update from web-platform-tests Reset trailing space structure when rewinding due to overflow handling During the HandleOverflow we consider the possibility of breaking at previous opportunity. The logic for this case is implemented in the BreakTextAtPreviousBreakOpportunity function. In case that there is such suitable previous opportunity, we modify the ItemResult that includes this opportunity in its offset range. We also create a new ShapeResultView associated to this item_result, using the new offset range. However, it's possible that the trailing_collapsible_space_ structure already has this ItemResult instance, that we are now altering as part of the HandleOverflow logic. The problem described in the issue 1131470 is caused by this situation, where an ItemResult instance hold by the trailing_collapsible_space_ is modified. During the computation of the trailing spaces size, as part of the RemoveTrailingCollapsibleSpace function, we avoid calling to the TruncateLineEndResult, which will reshape again, in case the item_result considered is already present in the trailing_collapsible_space_ structure. This causes that we end up with an ItemREsult of a different size than the previously computed collapsed_shape_result. Bug: 1131470 Change-Id: I15b31303fb8ec52b6d7359880f2785d16e1a0c59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429411 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#811115} -- wpt-commits: 1916d3f4f67ab06325b4f0f8ac65b5ebad404bf2 wpt-pr: 25795
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip