a484581afc4b7a204dc018ed1a435fcf56ade75f: Bug 1298219 - Don't fire oop-browser-crashed event if the browser has already flipped remoteness and moved on. r=billm, a=ritu
Mike Conley <mconley@mozilla.com> - Wed, 31 Aug 2016 18:23:40 -0400 - rev 350204
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1298219 - Don't fire oop-browser-crashed event if the browser has already flipped remoteness and moved on. r=billm, a=ritu 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
961603912962c62f9715751518358edc82f7afdf: Bug 1297419 - Ensure that APZ smooth scrolls don't get clobbered by the main thread as a side-effect of reflow. r=tnikkel, a=ritu
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 06 Sep 2016 14:43:41 -0400 - rev 350203
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1297419 - Ensure that APZ smooth scrolls don't get clobbered by the main thread as a side-effect of reflow. r=tnikkel, a=ritu MozReview-Commit-ID: 9124WMy8SmD
41184c8c63b17e62605e0f9840d8e3350ac2275a: Bug 1260324. Don't draw garbage to the screen if an image doesn't happen to be decoded. r=seth, a=ritu
Timothy Nikkel <tnikkel@gmail.com> - Wed, 24 Aug 2016 00:02:19 -0500 - rev 350202
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1260324. Don't draw garbage to the screen if an image doesn't happen to be decoded. r=seth, a=ritu Layout has been using imgIContainer::IsOpaque to determine if the image will draw opaquely to all pixels it covers, and doing culling based on this. However imgIContainer::IsOpaque doesn't guarantee anything. It only describes if the image, when in a decoded state, has all opaque pixels. So if the image doesn't have fully decoded frames around (because they got discarded) it may not draw opaquely to all of its pixels. So we create a new function that first checks if there is a fully decoded frame.
8fe577bafb7837433a3d88515baf0c4155dadf90: Bug 1294366 - Fix filter widget select opening only once, force focus on window on click. r=ochameau, a=ritu
Julian Descottes <jdescottes@mozilla.com> - Mon, 22 Aug 2016 17:55:12 +0200 - rev 350201
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1294366 - Fix filter widget select opening only once, force focus on window on click. r=ochameau, a=ritu MozReview-Commit-ID: 5xcZuoRxOco
0c2347afecab58733a57e88fae039df838f78c54: Bug 1297427 - Discount border dots with negative radii. r=jrmuizel, a=ritu
Bas Schouten <bschouten@mozilla.com> - Thu, 08 Sep 2016 14:00:54 +0200 - rev 350200
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1297427 - Discount border dots with negative radii. r=jrmuizel, a=ritu MozReview-Commit-ID: 1CONhbL8ZAb
dabeb362ff124c1af9325ae34fdd43e2038556ee: Bug 1297427 - Use calculate curve origin instead of reusing center curve origin in DottedCornerFinder. r=bas, a=ritu
Tooru Fujisawa <arai_a@mac.com> - Thu, 08 Sep 2016 10:14:14 +0900 - rev 350199
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1297427 - Use calculate curve origin instead of reusing center curve origin in DottedCornerFinder. r=bas, a=ritu
201882b9e76226bc970f38abd2d99a0e231669a4: Bug 1202200 - Skip browser_social_chatwindowfocus.js because it's flaky and unsupported at this point. a=test-only
Ryan VanderMeulen <ryanvm@gmail.com> - Tue, 13 Sep 2016 17:40:19 -0400 - rev 350198
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1202200 - Skip browser_social_chatwindowfocus.js because it's flaky and unsupported at this point. a=test-only
15daa0afa249e4a98ea85d03402aa09cf5eae20c: Bug 1273369 - Remove CPOW usage in browser_webconsole_bug_613280_jsterm_copy.js. r=bgrins, a=test-only
Kevin Chan <kevchan85@yahoo.com> - Fri, 09 Sep 2016 07:48:56 -0700 - rev 350197
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1273369 - Remove CPOW usage in browser_webconsole_bug_613280_jsterm_copy.js. r=bgrins, a=test-only MozReview-Commit-ID: 8fYEOrIZF72
dd74105957e26e3134fd6306473d7303cd6b0165: Bug 1281138 - Disable WebIDE test_simulators for intermittent failures. a=test-only
J. Ryan Stinnett <jryans@gmail.com> - Thu, 08 Sep 2016 17:59:34 -0500 - rev 350196
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1281138 - Disable WebIDE test_simulators for intermittent failures. a=test-only MozReview-Commit-ID: 6sXZ8v7zqL8
ab5dbae4c8e22ad92ce1bffbf0198396aeb4ccfc: Bug 931445 - Part 5 - Avoid childIframe subtest to be started twice. r=smaug, a=test-only
Xidorn Quan <me@upsuper.org> - Wed, 03 Aug 2016 15:14:49 +1000 - rev 350195
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 931445 - Part 5 - Avoid childIframe subtest to be started twice. r=smaug, a=test-only This is a silly bug that start() is called twice in this subtest, one from the load event of the document (by pointerlock_utils.js), the other is by onload of the iframe. Given the document's load event comes later, I removed the onload of iframe. MozReview-Commit-ID: 7TQJVa3xCb9
79429ecdadfa79a101cff2add3d5c1eac5b07e7f: bug 1301288 - set post update values earlier in startup so Firefox post update actions can be performed. r=mhowell, a=rkothari
Robert Strong <robert.bugzilla@gmail.com> - Tue, 13 Sep 2016 14:37:14 -0700 - rev 350194
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
bug 1301288 - set post update values earlier in startup so Firefox post update actions can be performed. r=mhowell, a=rkothari
696a981b6d534a7015d6f2ba3d2379af620e9b26: Bug 1297794 - Fix SetEntriesInAcl failure on non-English Windows version. r=aklotz, a=ritu
Kacper Michajlow <kasper93@gmail.com> - Wed, 24 Aug 2016 20:57:16 +0200 - rev 350193
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1297794 - Fix SetEntriesInAcl failure on non-English Windows version. r=aklotz, a=ritu MozReview-Commit-ID: 4FJBtUBjPEu
fd095a122f65c56fd1198468adbf280e59c6cfa7: Bug 1292310 - Enter may wrongly confirm a mouse selected entry in the urlbar. r=adw, a=ritu
Marco Bonardo <mbonardo@mozilla.com> - Tue, 06 Sep 2016 17:55:56 +0200 - rev 350192
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1292310 - Enter may wrongly confirm a mouse selected entry in the urlbar. r=adw, a=ritu MozReview-Commit-ID: 6teMoPr1vb6
76e76e26bfe70e13bf6c91bfb2530f9acc42687a: Bug 1299766 - Bring back contentpolicy check for websockets in child to avoid missing context for addon implemented content policies within parent. r=jduell, a=ritu
Christoph Kerschbaumer <ckerschb@christophkerschbaumer.com> - Mon, 05 Sep 2016 13:54:41 +0200 - rev 350191
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1299766 - Bring back contentpolicy check for websockets in child to avoid missing context for addon implemented content policies within parent. r=jduell, a=ritu
30ab4c8ae8d154f63d3bdad45b4ac2c4e15ea041: Bug 1274498 - Refuse to play H.264 files which have one or more dimensions less than 48 pixels. r=jya, a=ritu
Chris Pearce <cpearce@mozilla.com> - Wed, 07 Sep 2016 14:16:29 +1200 - rev 350190
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1274498 - Refuse to play H.264 files which have one or more dimensions less than 48 pixels. r=jya, a=ritu We've had large numbers of shutdown hangs with the Windows H.264 decoder stuck calling IMFTransform::ProcessOutput(), blocking shutdown. I can reproduce this with videos with dimensions less than 32 pixels. Chrome also encountered this with the WMF decoder: https://bugs.chromium.org/p/chromium/issues/detail?id=373288 The WMF H.264 Decoder is documented to have a minimum resolution of 48x48 pixels. So this patch causes us to reject H.264 files with either width or height less than 48 pixels. I have been able to play files down to 34x34 pixels on Windows 10, but it seems safest to just follow the what's documented in MSDN, and reject files that are smaller than the documented minimum. MozReview-Commit-ID: 5peP6UGnAaB
0a1f64d2110eb2f589a1615cab6d446bccbd5c87: Bug 1296275 - Be better about exposing to active js in AudioBuffer::StealJSArrayDataIntoSharedChannels(). r=terrence, a=ritu
Andrew McCreight <continuation@gmail.com> - Mon, 29 Aug 2016 15:03:42 -0700 - rev 350189
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1296275 - Be better about exposing to active js in AudioBuffer::StealJSArrayDataIntoSharedChannels(). r=terrence, a=ritu MozReview-Commit-ID: GC8sncFJlPS
df0e14b3f743afbc85a4c75a9e95789aedcf5c9a: Bug 1292159 - Be more careful about removing the inherit principal bit on base channel redirects. r=ckerschb, a=ritu
Boris Zbarsky <bzbarsky@mit.edu> - Fri, 02 Sep 2016 17:55:38 -0400 - rev 350188
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1292159 - Be more careful about removing the inherit principal bit on base channel redirects. r=ckerschb, a=ritu
89ba44134660cdcf954e00ce8b387b0fbaeb7db3: Bug 1246972 - Always require the update working directory to be within the installation path. r=rstrong, a=ritu
Matt Howell <mhowell@mozilla.com> - Thu, 25 Aug 2016 15:31:13 -0700 - rev 350187
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1246972 - Always require the update working directory to be within the installation path. r=rstrong, a=ritu This required fixing a few chrome tests which broke on Mac because they were assuming updater-settings.ini would be at the same location as the executables. Also, this patch removes many dependencies on the current working directory from updater.cpp by changing it to use absolute paths instead. Otherwise this patch would have required adding yet more chdir() calls to avoid invalidating existing assumptions about what the current directory is. MozReview-Commit-ID: ASxfV4uVpmD
404c54eecb4dcd1e9ee465ba054063471e310a5d: Bug 1291928 - Expose JSSavedStack's stack before returning. r=bz, a=ritu
Terrence Cole <terrence@mozilla.com> - Wed, 03 Aug 2016 16:12:51 -0700 - rev 350186
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1291928 - Expose JSSavedStack's stack before returning. r=bz, a=ritu
7f90dcc0445b8c06aa7529bb63dbed5991fc590d: Bug 1291437 - Followup: Add some comments explaining why we're initializing the AutoJSAPI in PostMessageEvent::Run the way we do. a=ritu
Boris Zbarsky <bzbarsky@mit.edu> - Tue, 02 Aug 2016 13:28:17 -0700 - rev 350185
Push 1230 by jlund@mozilla.com at Mon, 31 Oct 2016 18:13:35 +0000
Bug 1291437 - Followup: Add some comments explaining why we're initializing the AutoJSAPI in PostMessageEvent::Run the way we do. a=ritu
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip