f7fc4fab8018940bba5caf66e650592794f8a853: Bug 1277582 - Don't send HTTP constructor when content process has started to shut down (r=mrbkap)
Bill McCloskey <billm@mozilla.com> - Fri, 02 Sep 2016 16:23:00 -0700 - rev 312901
Push 30665 by cbook@mozilla.com at Wed, 07 Sep 2016 15:20:43 +0000
Bug 1277582 - Don't send HTTP constructor when content process has started to shut down (r=mrbkap)
a5029e21db2453b5147c0f842cb4c6e30b4600fa: Bug 1266836 - Part 4: Followup to fix a missed rename in Part 3. r=MattN
aleth <aleth@instantbird.org> - Mon, 05 Sep 2016 00:36:46 +0200 - rev 312900
Push 30665 by cbook@mozilla.com at Wed, 07 Sep 2016 15:20:43 +0000
Bug 1266836 - Part 4: Followup to fix a missed rename in Part 3. r=MattN
13a0934e2cc9625db2aff4a17f301e89bce4997d: Bug 1299596 - Handle failure to remove event listener in ChromeMessagePort.destroy. r=mconley
Eric Rahm <erahm@mozilla.com> - Tue, 06 Sep 2016 10:33:55 -0700 - rev 312899
Push 30665 by cbook@mozilla.com at Wed, 07 Sep 2016 15:20:43 +0000
Bug 1299596 - Handle failure to remove event listener in ChromeMessagePort.destroy. r=mconley It's possible this._browser is already a dead wrapper when trying to unregister the event listener. In that case we can carry on with destruction.
c27d9a2bc26136de943b9a114aa326db414cf6fb: Bug 1300139 - Handle JSON NPE in DownloadContentCatalog; r=sebastian
Geoff Brown <gbrown@mozilla.com> - Tue, 06 Sep 2016 11:31:03 -0600 - rev 312898
Push 30665 by cbook@mozilla.com at Wed, 07 Sep 2016 15:20:43 +0000
Bug 1300139 - Handle JSON NPE in DownloadContentCatalog; r=sebastian
a14f88a9af7a59e677478694bafd9375ac53683e: merge fx-team to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Wed, 07 Sep 2016 17:13:53 +0200 - rev 312897
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
merge fx-team to mozilla-central a=merge
041a925171e431bf51fb50193ab19d156088c89a: Bug 1295010 - Removed testActor from highlighterHelper in inspector tests; r=me
Patrick Brosset <pbrosset@mozilla.com> - Wed, 07 Sep 2016 11:10:49 +0200 - rev 312896
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1295010 - Removed testActor from highlighterHelper in inspector tests; r=me MozReview-Commit-ID: GMksl81iGcp
541c9086c0f27fba60beecc9bc94543103895c86: Bug 1299154 - added Set/GetOverrideDPPX to restorefromHistory; r=mstange
Matteo Ferretti <mferretti@mozilla.com> - Wed, 31 Aug 2016 09:51:46 +0200 - rev 312895
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1299154 - added Set/GetOverrideDPPX to restorefromHistory; r=mstange MozReview-Commit-ID: AsyAcG3Igbn
a6b6a93eb41a05e310a11f0172f01ba9b21d3eac: Bug 1295010 - Don't move the eyedropper to the out of browser window by keyboard navigation. r=pbro
Ruturaj Vartak <ruturaj@gmail.com> - Sat, 03 Sep 2016 00:07:00 +0200 - rev 312894
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1295010 - Don't move the eyedropper to the out of browser window by keyboard navigation. r=pbro MozReview-Commit-ID: vBwmSxVNXK
99c542fa43a72ee863c813b5624048d1b443549b: Bug 1300336 - Allow pseudo-arrays to have a length property. r=fitzgen
Oriol <oriol-bugzilla@hotmail.com> - Sat, 03 Sep 2016 12:46:00 -0400 - rev 312893
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1300336 - Allow pseudo-arrays to have a length property. r=fitzgen
16a1a91f9269ab95dd83eb29dc5d0227665f7d94: Bug 1296648 - Fix direction of .ruleview-expander.theme-twisty in RTL locales. r=ntim
Towkir Ahmed <towkir17@gmail.com> - Sat, 03 Sep 2016 22:53:00 -0400 - rev 312892
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1296648 - Fix direction of .ruleview-expander.theme-twisty in RTL locales. r=ntim
73a6a267a50a0e1c41e689b265ad3eebe43d7ac6: Merge m-c to fx-team, a=merge
Wes Kocher <wkocher@mozilla.com> - Tue, 06 Sep 2016 17:37:18 -0700 - rev 312891
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Merge m-c to fx-team, a=merge
ae2144aa4356b65c2f8c0de8c9082dcb7e330e24: Bug 1300866 - expose devtools require to new debugger r=jlast,bgrins
James Long <longster@gmail.com> - Tue, 06 Sep 2016 17:17:35 -0400 - rev 312890
Push 30664 by cbook@mozilla.com at Wed, 07 Sep 2016 15:14:08 +0000
Bug 1300866 - expose devtools require to new debugger r=jlast,bgrins
3d0b41fdd93bd8233745eadb4e0358e385bf2cb9: Bug 1295453 - Don't wait for data to be sent when closing socket immediately r=jdm
William Lachance <wlachance@mozilla.com> - Tue, 06 Sep 2016 15:51:51 -0400 - rev 312889
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1295453 - Don't wait for data to be sent when closing socket immediately r=jdm We can't guarantee any data will be written, it should suffice to just make sure that the socket closes immediately and then verify that a complete set of data wasn't read. MozReview-Commit-ID: CHHuJEGRVgX
66324402a18bb01a39f533aaabff0f202d89cc94: Bug 1291172 Add eQueryTextRectArray tests which compare with eQueryTextRect result r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 06 Sep 2016 18:59:40 +0900 - rev 312888
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1291172 Add eQueryTextRectArray tests which compare with eQueryTextRect result r=smaug eQueryTextRect is used by widget and eQueryTextRectArray is used by ContentCacheInChild. So, matching their result guarantees that widget can get same result both in non-e10s mode and e10s mode. So, the matching should be tested. MozReview-Commit-ID: 6GfbyvZ9X7H
8a0e581059ccfb773238873d4c218c9d07e137bb: Bug 1296217 ContentEventHandler::OnQueryTextRectArray() should apply CSS transform to each character or line breaker rect r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 06 Sep 2016 11:46:31 +0900 - rev 312887
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1296217 ContentEventHandler::OnQueryTextRectArray() should apply CSS transform to each character or line breaker rect r=smaug Currently, ContentEventHandler::OnQueryTextRectArray() is used only in e10s mode (at caching necessary character rects in ContentCacheInChild). Therefore, this bug occurs only in e10s mode. ContentEventHandler::OnQueryTextRectArray() applies CSS transform only to each frame rect. Therefore, character rect's width and height are not applied. This patch makes the loop apply CSS transform to each character or line breaker rect (i.e., each item of charRects). Then, we need to rewrite the lastCharRect hack. It stores the last charRect value for computing next line breaker rect if next line breaker is caused by a block level element or something, i.e., not caused by a <br> frame. So, when brRect is computed with lastCharRect, the loop needs to apply CSS transform of the last text frame to the following brRect because it tries to compute a caret rect immediately after the last character. For doing this, this patch adds lastFrame which stores the last frame for lastCharRect and set it to baseFrame. Then, at applying CSS transform to each charRect, it can apply CSS transform of expected frame. Similarly, when brRect is computed with last text frame, this patch looks for the last text frame from lastTextContent and use it as base frame to apply to CSS transform. MozReview-Commit-ID: 5Yr2HMrooHd
cfd5f330f1158682b0b109de50b679d3329f12fc: Merge m-c to autoland, a=merge
Wes Kocher <wkocher@mozilla.com> - Tue, 06 Sep 2016 17:36:41 -0700 - rev 312886
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Merge m-c to autoland, a=merge
bd4d11e10ee28439add0cbfbf7c99f25a662a82e: Bug 1298219 - Regression test. r=billm
Mike Conley <mconley@mozilla.com> - Thu, 01 Sep 2016 13:10:37 -0400 - rev 312885
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1298219 - Regression test. r=billm MozReview-Commit-ID: 5sDWL9NuTso
804c98e6fef45ffd4cbaef194e94fec3b578068f: Bug 1298219 - Don't fire oop-browser-crashed event if the browser has already flipped remoteness and moved on. r=billm
Mike Conley <mconley@mozilla.com> - Wed, 31 Aug 2016 18:23:40 -0400 - rev 312884
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1298219 - Don't fire oop-browser-crashed event if the browser has already flipped remoteness and moved on. r=billm We currently make the initial browser in a window remote by default. If early on in the session, that one remote browser goes away (and the content process was still booting), there's about 5 seconds before the shutdown kill timer will take that content process out for not quitting fast enough. There are some cases during startup where the content process is waiting on information from the parent, so it cannot respond to the request to quit in time. The parents shutdown kill timer goes off, and the shutdown kill occurs. In this bug, what's happening is that the initial browser flips remoteness from remote to non-remote when it goes to about:sessionrestore. This starts the shutdown kill timer. The content process runs out of time, and the shutdown kill timer fires, killing the content process. The TabParent::ActorDestroy method (which still exists, even though the browser is no longer remote), interprets this as an abnormal shutdown, and bubbles the oop-browser-crashed event to the associated <xul:browser>, which causes the page to browser to about:tabcrashed, when it had already loaded about:sessionrestore. This patch makes it so that the TabParent::ActorDestroy method first checks to ensure that the associated remote frameloader is still the one that the frameloader owner cares about. If not (because, say, the remoteness has flipped and a new non-remote frameloader has been created), then the event is not fired, since the user has moved on. MozReview-Commit-ID: G4jmR6lMMFl
a093339f5b6181440201bcf747c9013da11c4bda: Bug 1299984 - Enable eslint no-unused-vars for shipping pwmgr code. r=johannh
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Fri, 02 Sep 2016 14:07:13 -0700 - rev 312883
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1299984 - Enable eslint no-unused-vars for shipping pwmgr code. r=johannh I also fixed two test cases while I was looking at the results. MozReview-Commit-ID: LpUj56UNV3r
17f792799636c637c96229e877a2f1b93edcd147: Bug 1300820 - Always use the current debugger frontend in Browser Toolbox;r=jlongster
Brian Grinstead <bgrinstead@mozilla.com> - Tue, 06 Sep 2016 11:20:38 -0700 - rev 312882
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1300820 - Always use the current debugger frontend in Browser Toolbox;r=jlongster MozReview-Commit-ID: DJ7L2VSOe2q
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip