13adabb755622b9cb85f76e2e15808e64296c412: Backed out 7 changesets (bug 1440177) for build bustages on a CLOSED TREE
arthur.iakab <aiakab@mozilla.com> - Thu, 01 Mar 2018 23:45:23 +0200 - rev 406153
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Backed out 7 changesets (bug 1440177) for build bustages on a CLOSED TREE Backed out changeset d83a1820b2f2 (bug 1440177) Backed out changeset a77d06b2cf03 (bug 1440177) Backed out changeset 928770efc9a3 (bug 1440177) Backed out changeset 49b285030492 (bug 1440177) Backed out changeset 717a696b17e0 (bug 1440177) Backed out changeset 0840994846bf (bug 1440177) Backed out changeset b1ba6c67264b (bug 1440177)
d83a1820b2f22263888e082911615e0c5dd4288f: Bug 1440177 - Part 7: Don't allocate new clips when flattening nsDisplayOpacity. r=mstange
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 02 Mar 2018 10:06:13 +1300 - rev 406152
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 7: Don't allocate new clips when flattening nsDisplayOpacity. r=mstange Combing the two clips as-is should always be correct, and since they're frequently identical, we can usually make IntersectClip a no-op. MozReview-Commit-ID: EKHdPogzd3t
a77d06b2cf03b3b8824130a1e32c0b09d3ec138c: Bug 1440177 - Part 6: Don't dereference display items during AddPaintedDisplayItem for the LAYER_NONE case. r=jnicol
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 02 Mar 2018 10:06:13 +1300 - rev 406151
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 6: Don't dereference display items during AddPaintedDisplayItem for the LAYER_NONE case. r=jnicol The display items are almost certainly gone from the cache at this point, so dereferencing them can take a while. This moves the DisplayItemData lookup, and the IsReused/HasMergedFrames checks into the ProcessDisplayItems pass (where we already use the items), and then just uses the AssignedDisplayItem entry for everything. MozReview-Commit-ID: JrRshEyZncb
928770efc9a3dab8eedf0e97357bd475d67c724a: Bug 1440177 - Part 5: Don't call GetDisplayItemDataForManager in AddPaintedDisplayItem since we already have it passed in as a parameter. r=jnicol
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 19 Feb 2018 12:37:01 +1300 - rev 406150
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 5: Don't call GetDisplayItemDataForManager in AddPaintedDisplayItem since we already have it passed in as a parameter. r=jnicol MozReview-Commit-ID: IHrVPutPSC5
49b285030492a1f490844fa721750def4fc4d112: Bug 1440177 - Part 4: Avoid expensive hashtable lookups in PaintedLayerDataTree when we're in an inactive layer and want all items in the same layer. r=mstange
Matt Woodrow <mwoodrow@mozilla.com> - Thu, 15 Feb 2018 15:52:37 +1300 - rev 406149
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 4: Avoid expensive hashtable lookups in PaintedLayerDataTree when we're in an inactive layer and want all items in the same layer. r=mstange MozReview-Commit-ID: 6brxIaZR2eq
717a696b17e07a91edf9b6cbf9be0a611aea1f40: Bug 1440177 - Part 3: Preallocate a small number of PaintedLayerData objects and only resize the mPaintedLayerDataStack once. r=jnicol
Matt Woodrow <mwoodrow@mozilla.com> - Thu, 15 Feb 2018 14:45:35 +1300 - rev 406148
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 3: Preallocate a small number of PaintedLayerData objects and only resize the mPaintedLayerDataStack once. r=jnicol MozReview-Commit-ID: 1LIxNSVHHkp
0840994846bf50d1278920a8a677603f29e26582: Bug 1440177 - Part 2: Combine PaintedLayerItemsEntry and PaintedDisplayItemLayerUserData into a single struct. r=jnicol
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 13 Feb 2018 15:56:43 +1300 - rev 406147
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 2: Combine PaintedLayerItemsEntry and PaintedDisplayItemLayerUserData into a single struct. r=jnicol These two structs store very similar state (including duplicating the mask layer common clip count), and the former uses an expensive hashtable for lookups. This patch combines the two, and uses a vector of entries instead of the hashtable so we can do the cleanup pass. * * * [mq]: fix MozReview-Commit-ID: KamhbGAIqpD
b1ba6c67264bce7b38de085b41183a5029023127: Bug 1440177 - Part 1: Don't call GetLayerState from BuildContainerLayerFor as it recurses into child display items to find the answer. r=jnicol
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 13 Feb 2018 14:25:55 +1300 - rev 406146
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440177 - Part 1: Don't call GetLayerState from BuildContainerLayerFor as it recurses into child display items to find the answer. r=jnicol MozReview-Commit-ID: 3A4OBC5L6Ps
017d83ffe0a47a22d342ab61224ca09977a308a5: Bug 1425152 - Update lastSync timestamp even if some sync engines failed r=markh
Thom Chiovoloni <tchiovoloni@mozilla.com> - Tue, 20 Feb 2018 18:56:35 -0500 - rev 406145
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1425152 - Update lastSync timestamp even if some sync engines failed r=markh MozReview-Commit-ID: HTWuZsp5Evb
3aa4c86bbf163e222d9789f9f43912e7d24b3763: Bug 1435067 - Use the pingsender when sending the sync ping r=gfritzsche,markh
Thom Chiovoloni <tchiovoloni@mozilla.com> - Thu, 01 Feb 2018 16:38:41 -0500 - rev 406144
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1435067 - Use the pingsender when sending the sync ping r=gfritzsche,markh MozReview-Commit-ID: 2x98suZvfr0
885ab31f399bc91eeb70d4721e2c6c90e56508fc: Bug 1441666 - Add helper functions for inserting encrypted records to the test server r=kitcambridge
Thom Chiovoloni <tchiovoloni@mozilla.com> - Wed, 21 Feb 2018 16:35:45 -0500 - rev 406143
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1441666 - Add helper functions for inserting encrypted records to the test server r=kitcambridge This also converts some of our tests to use them. In particular, 1. All of the new functions should have coverage. 2. None of the existing tests should assume we can decrypt records by JSON.parsing them. MozReview-Commit-ID: y7Hw3q9Wko
87d555dea4f47cf097bc6264ee669b5251a2a696: Bug 1370930 - remove DirectoryLinksProvider, r=Mardak
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Thu, 01 Mar 2018 16:53:49 +0000 - rev 406142
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1370930 - remove DirectoryLinksProvider, r=Mardak MozReview-Commit-ID: 4YcsNvRg7Hn
4c6f709a5e54887d405d3bec931933f7f4a53df0: Bug 1420078 - Increase some talos job max runtimes for some tests that areborderline and intermittently timing out; r=jmaher
Rob Wood <rwood@mozilla.com> - Thu, 01 Mar 2018 13:14:26 -0500 - rev 406141
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1420078 - Increase some talos job max runtimes for some tests that areborderline and intermittently timing out; r=jmaher MozReview-Commit-ID: GqSBkpN7RoU
d4ed9c1d6ba75db9c93cbd7e5c876071413dc7ad: Bug 1438985 fix showing hidden tabs on extension shutdown, r=aswan
Shane Caraveo <scaraveo@mozilla.com> - Thu, 01 Mar 2018 12:04:52 -0600 - rev 406140
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1438985 fix showing hidden tabs on extension shutdown, r=aswan We need a static disable event so we can handle shutdown of extensions using hidden tabs. This allows us to handle shutdown when the extension has not yet used the API (thus the ext-tabs api has not loaded). MozReview-Commit-ID: BxV5PmbHJ8o
0d138609abfd31b2e0ba7ef1d8fca67e4942bb0f: Bug 1344749 - Expose API to customize where new tabs open, r=dao,mixedpuppy
Bob Silverberg <bsilverberg@mozilla.com> - Fri, 19 Jan 2018 12:59:53 -0500 - rev 406139
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1344749 - Expose API to customize where new tabs open, r=dao,mixedpuppy This patch implements the preference "browser.tabs.insertAfterCurrent" which, when set to true, will cause all tabs (related and unrelated) to be opened next to the current tab. It also implements the browserSettings API "newTabPosition", which allows extensions to control both "browser.tabs.insertRelatedAfterCurrent", and "browser.tabs.insertAfterCurrent" via values for "afterCurrent", "relatedAfterCurrent" and "atEnd". The code for "browser.tabs.insertAfterCurrent" including the test for it is mostly taken from a patch attached to bug 933532 written by Masayuki Nakano. MozReview-Commit-ID: KQE7M2FGpc7
30b45ad3b81ada48f1924c16035e6bf7926c4474: Bug 1442377 - Move fillSubviewFromMenuItems/clearSubview to CustomizableUI.jsm. r=Gijs
Mark Banner <standard8@mozilla.com> - Thu, 01 Mar 2018 19:53:07 +0000 - rev 406138
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1442377 - Move fillSubviewFromMenuItems/clearSubview to CustomizableUI.jsm. r=Gijs MozReview-Commit-ID: BQ8V39C68WO
406c8d7d134fd094469ed7910a28696a8a5330af: Bug 1429186 - Create an enterprise policy to set the homepage and, optionally, lock it r=Felipe
Kirk Steuber <ksteuber@mozilla.com> - Tue, 27 Feb 2018 09:13:16 -0800 - rev 406137
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1429186 - Create an enterprise policy to set the homepage and, optionally, lock it r=Felipe Also creates the runOncePerModification helper function in Policies.jsm and fixes a minor bug in the runOnce helper function also in Policies.jsm MozReview-Commit-ID: HDgMmhHI1D0
413a684727a20b4c4a0e0aa06244faa14e1be401: Bug 1442028 - Move webdriver actions into its own module. r=ato
Henrik Skupin <mail@hskupin.info> - Wed, 28 Feb 2018 22:31:47 +0100 - rev 406136
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1442028 - Move webdriver actions into its own module. r=ato MozReview-Commit-ID: Bf0Ut8AGwtl
18dd09f4f5ba3a2d1f0f11ae8fa192b5805b728c: Bug 1440276 - Activity Stream spikes after Bookmark activity, triggering lots of main thread work r=mak
Ursula Sarracini <usarracini@mozilla.com> - Wed, 28 Feb 2018 11:17:42 -0500 - rev 406135
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
Bug 1440276 - Activity Stream spikes after Bookmark activity, triggering lots of main thread work r=mak MozReview-Commit-ID: BoCZEDXpSKD
3dc52ab4b2e22b13abfc8d7ea64762dc277850df: servo: Merge #20152 - Support zero rowspans (from Manishearth:rowspan-zero); r=mbrubeck
Manish Goregaokar <manishsmail@gmail.com> - Thu, 01 Mar 2018 13:36:43 -0500 - rev 406134
Push 33545 by aciure@mozilla.com at Fri, 02 Mar 2018 10:14:13 +0000
servo: Merge #20152 - Support zero rowspans (from Manishearth:rowspan-zero); r=mbrubeck This makes rowspan=0 work by storing notes on which group of rows we're in for tables containing both rowgroups and rows, and using that to respan cells with overlarge or zero rowspans. This also gets rid of the largest_leftover_incoming_size business, because now spans will always be correct and we'll never have any left over. Based on https://github.com/servo/servo/pull/20128 r? @mbrubeck Source-Repo: https://github.com/servo/servo Source-Revision: 6f2cd86b8ee7bbe71ff30758cf5c2174e008e9b5
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip