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
60856a997b32a1866523c230e4a73509d78ea568: Bug 1300442 - Housekeeping and QoL changes: code style, extra logging on VP. r=maja_zf
Bryce Van Dyk <bvandyk@mozilla.com> - Mon, 05 Sep 2016 11:02:07 +1200 - rev 312881
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1300442 - Housekeeping and QoL changes: code style, extra logging on VP. r=maja_zf - Use format() instead of old style formatting (%s, etc). - Remove unneeded positional args on format strings. - Break some long lines for pep8 conformance. - Use brackets instead of \ to continue long lines. - Log interval on video puppeteer. - Remove an unneeded media source check. We have explicit media source checks in tests, and the media source prefix has changed, rendering the check broken. MozReview-Commit-ID: 4FPVoOD0P5B
89b9735661b9f19ece9b6a2bb54b1c50d0556b34: Bug 1288193 - Ensure that the content process receives the presentation status of a VRDisplay immediately after adding or removing layers r=gw280
kearwood - Fri, 02 Sep 2016 14:45:54 -0700 - rev 312880
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1288193 - Ensure that the content process receives the presentation status of a VRDisplay immediately after adding or removing layers r=gw280 - Corrects issues with the onvrdisplaypresentationchange events being delayed by up to 5 seconds. - Caused a delay to enter or exit WebVR presentation on many sites. MozReview-Commit-ID: 2LACZNwKIxW
cf5ad16b4d9eeb347d44fab3e7f0d2066eb752e4: Bug 1296403 - Update tooltool rustc to 1.11.0. r=mshal
Ralph Giles <giles@mozilla.com> - Tue, 06 Sep 2016 13:09:56 -0700 - rev 312879
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1296403 - Update tooltool rustc to 1.11.0. r=mshal Repacks of upstream builds of rust 1.11.0 stable with std libraries for the appropriate targets. Remove the separate rust-std package references since the new repacks include the necessary targets. Also update clang and hazard builds to the latest toolchain. MozReview-Commit-ID: K7oBxQZnLPu
2e6b9e57d5a0527bd51f86be22e930acf450cf8d: Backed out 2 changesets (bug 1298219) for asan bc5 crashes a=backout
Wes Kocher <wkocher@mozilla.com> - Tue, 06 Sep 2016 14:40:32 -0700 - rev 312878
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Backed out 2 changesets (bug 1298219) for asan bc5 crashes a=backout Backed out changeset 98b0e9b88212 (bug 1298219) Backed out changeset 5948ae1f4218 (bug 1298219)
d090231db437d7bf918f97f419c0c858882658b3: Bug 1294291 - Remove missing GUID handling code from Sync and Places. r=markh
Kit Cambridge <kcambridge@mozilla.com> - Tue, 06 Sep 2016 11:29:32 -0700 - rev 312877
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1294291 - Remove missing GUID handling code from Sync and Places. r=markh MozReview-Commit-ID: CbhF4s0nNr0
556e6c27c5ca33cd7f21bd7ad1be3c8976da909d: Bug 1297419 - Ensure that APZ smooth scrolls don't get clobbered by the main thread as a side-effect of reflow. r=tnikkel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 06 Sep 2016 14:43:41 -0400 - rev 312876
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1297419 - Ensure that APZ smooth scrolls don't get clobbered by the main thread as a side-effect of reflow. r=tnikkel MozReview-Commit-ID: 9124WMy8SmD
a9e15f6064208d65164c60384d763741dcc708fa: Bug 1300124 - make MurmurHash3.cpp compile with clang-cl; r=bkelly
Nathan Froyd <froydnj@mozilla.com> - Tue, 06 Sep 2016 15:46:01 -0400 - rev 312875
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1300124 - make MurmurHash3.cpp compile with clang-cl; r=bkelly Including headers inside anonymous namespaces, especially standard headers, is super-unusual; let's just move the header to the toplevel instead. MozReview-Commit-ID: CNykWQA5ndY
4266dca3ab7df795abc8865beb0aacc5884ffbfc: Bug 1299653 - Don't have the page scrolling when the tab is closed. r=jaws
Eitan Isaacson <eitan@monotonous.org> - Sat, 03 Sep 2016 14:14:29 -0700 - rev 312874
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1299653 - Don't have the page scrolling when the tab is closed. r=jaws MozReview-Commit-ID: DlmXfQQttRr
98b0e9b8821221843b17a1e191fae13a29e24018: Bug 1298219 - Regression test. r=billm
Mike Conley <mconley@mozilla.com> - Thu, 01 Sep 2016 13:10:37 -0400 - rev 312873
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
5948ae1f421848c2b998494dad665e140b768fc1: 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 312872
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
fafc28ee1d5d1537c790c8d03f1ee34fce0f0204: Bug 1300776 - Add testing/marionette/harness to flake8 linter (except mixins, tests) . r=ahal
Henrik Skupin <mail@hskupin.info> - Tue, 06 Sep 2016 15:46:08 +0200 - rev 312871
Push 30663 by cbook@mozilla.com at Wed, 07 Sep 2016 15:12:31 +0000
Bug 1300776 - Add testing/marionette/harness to flake8 linter (except mixins, tests) . r=ahal MozReview-Commit-ID: F9Hfze9zvzE
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip