6c1e3e522c60e3f0268e013558e940ce81aaf238: Bug 1444625 - Set gBrowser properties directly on the object rather than sequentially in init(). r?gijs draft
Dão Gottwald <dao@mozilla.com> - Sat, 10 Mar 2018 19:22:50 +0100 - rev 765898
Push 102176 by dgottwald@mozilla.com at Sat, 10 Mar 2018 18:23:31 +0000
Bug 1444625 - Set gBrowser properties directly on the object rather than sequentially in init(). r?gijs MozReview-Commit-ID: 3fBLokkFMnP
b54c375e96ac2b570f607f39cb500792695f4a88: Bug 1444628 - Fix a bunch of typo in the doc r?ahal draft
Sylvestre Ledru <sledru@mozilla.com> - Sat, 10 Mar 2018 17:14:38 +0100 - rev 765897
Push 102175 by sledru@mozilla.com at Sat, 10 Mar 2018 16:15:11 +0000
Bug 1444628 - Fix a bunch of typo in the doc r?ahal MozReview-Commit-ID: SNXsViVUm0
00027d9ec9f55e1478bbc1e5b3956b86d0fc93cd: Bug 1402549 - Part 2 - Use something else to trigger session store activity. r?esawin draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 10 Mar 2018 14:19:23 +0100 - rev 765896
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1402549 - Part 2 - Use something else to trigger session store activity. r?esawin Instead of adding and immediately closing a tab, which carries the risk that we catch a session store file that was written just in-between those two operations (although part 1 means that we should be able to handle this safely now), we just reload the current tab. MozReview-Commit-ID: JbiH8rmbbwJ
f5e97da739be61b209e0c7985634e3d8dc168403: Bug 1402549 - Part 1 - Assert number of saved tabs, too. r?esawin draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 10 Mar 2018 14:09:03 +0100 - rev 765895
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1402549 - Part 1 - Assert number of saved tabs, too. r?esawin MozReview-Commit-ID: DIfqQo3Fvlg
c07bcb3852bbbfa9e4a079eca4bde4d9567cdf91: debug logging draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 02 Mar 2018 18:16:43 +0100 - rev 765894
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
debug logging
c1a4d968af6cbe70b160bbef2594e210da6f683d: Bug 1414084 - Part 4 - Fix setting of private browsing theme state. r?grisha draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 02 Mar 2018 18:01:28 +0100 - rev 765893
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1414084 - Part 4 - Fix setting of private browsing theme state. r?grisha Previously, this wasn't noticeable since adding/removing a PageAction would call refreshPageActionIcons(), which would do the correct thing, but now a newly created PageActionLayout can start with an already pre-populated mPageAction- List, which means that the subsequently arriving call to setPrivateMode() will erroneously activate the private mode tinting for all PageActions that support it. MozReview-Commit-ID: EvNx1Q9vwZ5
31094ce7f8a64623f54311a864cc4f3960dda53c: Bug 1414084 - Part 3 - Correctly remove already resolved PageActions, too. r?grisha draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 03 Mar 2018 18:11:57 +0100 - rev 765892
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1414084 - Part 3 - Correctly remove already resolved PageActions, too. r?grisha When a PageActions:Remove message arrives and we cannot simply forward it, we need to remove not just pending PageActions:Add messages, but also any already present PageActions objects that a former PageActionLayout had handed to us. MozReview-Commit-ID: 3jnGsmMuVfa
129301f2c6e9660bdfb39ae291820cac43c84267: Bug 1414084 - Part 2 - Cache PageActions. r?grisha draft
Jan Henning <jh+bugzilla@buttercookie.de> - Mon, 26 Feb 2018 21:50:50 +0100 - rev 765891
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1414084 - Part 2 - Cache PageActions. r?grisha Since converting a PageAction message into an actual PageAction object also en- tails parsing the image data URL into a drawable, we leave that task to the PageActionLayout. This means that the PageAction cache needs to operate slightly differently than the MenuItem cache. First, we store all PageAction BundleEvent messages that arrive while no PageActionLayout is ready and then forward them en masse when one is ready. Secondly, if the PageActionLayout is going away again, we then also take a list of already parsed PageAction objects for safekeeping. MozReview-Commit-ID: AcPPONXqe46
c6d4d0f89bc24a0747e9be1cf8d7b7d9b5344dc3: Bug 1414084 - Part 1 - Move add-on menu item cache out of BrowserApp. r?grisha draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 25 Feb 2018 22:22:37 +0100 - rev 765890
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1414084 - Part 1 - Move add-on menu item cache out of BrowserApp. r?grisha Bug 832990 solved the issue of us losing the menu item cache if BrowserApp was destroyed, however the issue remains that we'll miss any Menu:... messages that are sent while BrowserApp doesn't exist, e.g. if Gecko is initially loaded through a GeckoView-based activity. Therefore we now move the menu item cache and the listener for those messages into a separate class whose lifetime better matches that of Gecko. MozReview-Commit-ID: BJleonLnjmo
d06fe31953b5d749930865975a8b552908fb63a2: Bug 1414084 - Part 0 - Cleanups. r? draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 25 Feb 2018 20:53:01 +0100 - rev 765889
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Bug 1414084 - Part 0 - Cleanups. r? MozReview-Commit-ID: B3ZGN2X8JXH
0929dd4832774efa334194fc4eabb9b0a84f5d26: Local build tweaks and base commit draft
Jan Henning <jh+bugzilla@buttercookie.de> - Thu, 28 Jul 2016 20:04:34 +0200 - rev 765888
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Local build tweaks and base commit MozReview-Commit-ID: H5pdKja8p2a
a5729ed955d609179496fd7cefcbafb8eb9ce9cf: Hobbesfox draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 12 Aug 2017 22:07:29 +0200 - rev 765887
Push 102174 by mozilla@buttercookie.de at Sat, 10 Mar 2018 16:08:47 +0000
Hobbesfox MozReview-Commit-ID: JVp98nUnBMo
c2fd8bcf8a815f28eed4d43fb55be7a5c839af26: Bug 1444625 - Set gBrowser properties directly on the object rather than sequentially in init(). r?gijs draft
Dão Gottwald <dao@mozilla.com> - Sat, 10 Mar 2018 17:02:55 +0100 - rev 765886
Push 102173 by dgottwald@mozilla.com at Sat, 10 Mar 2018 16:03:46 +0000
Bug 1444625 - Set gBrowser properties directly on the object rather than sequentially in init(). r?gijs MozReview-Commit-ID: DZmfD1ScYpR
7ee8b826b001bda6980fa2e755b38463341b81fe: Bug 1444530 - Set --tab-min-width in the tabs binding rather than gBrowser.init. r=gijs draft
Dão Gottwald <dao@mozilla.com> - Sat, 10 Mar 2018 12:13:47 +0100 - rev 765885
Push 102173 by dgottwald@mozilla.com at Sat, 10 Mar 2018 16:03:46 +0000
Bug 1444530 - Set --tab-min-width in the tabs binding rather than gBrowser.init. r=gijs MozReview-Commit-ID: E4EJKerJAng
4bff5b3dbc39f3e1505e8392eff252874c04ca95: Bug 1444594 - set correct prop-types in RequstListContent to clean up some warnings draft
glowka <glowka.tom@gmail.com> - Sat, 10 Mar 2018 16:33:14 +0100 - rev 765884
Push 102172 by bmo:glowka.tom@gmail.com at Sat, 10 Mar 2018 15:51:12 +0000
Bug 1444594 - set correct prop-types in RequstListContent to clean up some warnings MozReview-Commit-ID: K4dOSEVSAWN
3e0882632df464cd63d6b8eb5ddf84567aba7f5f: Bug 1444082 - sync reader mode to github tip ( 8525c6af36d3badbe27c4672a6f2dd99ddb4097f ), r?johannh draft
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Thu, 08 Mar 2018 14:35:02 +0000 - rev 765883
Push 102171 by gijskruitbosch@gmail.com at Sat, 10 Mar 2018 14:46:30 +0000
Bug 1444082 - sync reader mode to github tip ( 8525c6af36d3badbe27c4672a6f2dd99ddb4097f ), r?johannh MozReview-Commit-ID: LZLFf9kyUR5
7edf3d740fec1bf717cd151b1cf037b4a6b3a939: Bug 1444614 - Avoid initializing gBrowser and gBrowser.tabContainer early in the urlbar binding constructor. r?gijs draft
Dão Gottwald <dao@mozilla.com> - Sat, 10 Mar 2018 15:02:33 +0100 - rev 765882
Push 102170 by dgottwald@mozilla.com at Sat, 10 Mar 2018 14:02:59 +0000
Bug 1444614 - Avoid initializing gBrowser and gBrowser.tabContainer early in the urlbar binding constructor. r?gijs MozReview-Commit-ID: Lfv4d8RzhmZ
b45e0e7382990000b8e6e4c56ac9ea55b998af85: Bug 1437295 - Ensure that we have a compositor APZ testdata before running the test. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 10 Mar 2018 08:57:39 -0500 - rev 765881
Push 102169 by kgupta@mozilla.com at Sat, 10 Mar 2018 13:59:08 +0000
Bug 1437295 - Ensure that we have a compositor APZ testdata before running the test. r?botond MozReview-Commit-ID: D2ZRvg7mQra
d349d3b3b97c7e59bc82946a02909fca06394560: Bug 1437295 - Remove unnecessary change from bug 1374166. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 10 Mar 2018 08:57:38 -0500 - rev 765880
Push 102169 by kgupta@mozilla.com at Sat, 10 Mar 2018 13:59:08 +0000
Bug 1437295 - Remove unnecessary change from bug 1374166. r?botond The change that was made in bug 1374166 was attempting to fix the problem fixed by the previous patch, but didn't actually succeed (it just made it less likely to occur). Now that we have the proper fix we can revert that botched attempt to speed up the test a little bit. MozReview-Commit-ID: 871teQA40w6
d394c353b5701db101119aa5724b7fbcb3dcf07d: Bug 1437295 - Ensure that waitUntilApzStable also flushes the parent process. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 10 Mar 2018 08:57:38 -0500 - rev 765879
Push 102169 by kgupta@mozilla.com at Sat, 10 Mar 2018 13:59:08 +0000
Bug 1437295 - Ensure that waitUntilApzStable also flushes the parent process. r?botond With e10s enabled, we need to make sure that not only has the content process layer tree reached the compositor, but also that the parent process layer tree with the correct RefLayer has reached the compositor. This is important for some APZ tests which proceed on the assumption that the content process has been composited. MozReview-Commit-ID: DUFUNlJFbm6
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip