c7bed3468b5d85f9bf82eb72d1a0b9fbffd6a4fc: Bug 1261471: Remove support for getting mozIDOMWindowProxy via GetInterface. r=mrbkap
Kyle Huey <khuey@kylehuey.com> - Tue, 05 Apr 2016 20:14:14 -0700 - rev 291826
Push 74685 by khuey@mozilla.com at Wed, 06 Apr 2016 03:21:47 +0000
Bug 1261471: Remove support for getting mozIDOMWindowProxy via GetInterface. r=mrbkap
472ddbb34a370a4876b3ac3a953b4f0474592a4c: Bug 1261814: Use the presence of the content global, and not any random global, to determine whether to run the close handler. r=bz
Kyle Huey <khuey@kylehuey.com> - Tue, 05 Apr 2016 20:12:56 -0700 - rev 291825
Push 74685 by khuey@mozilla.com at Wed, 06 Apr 2016 03:21:47 +0000
Bug 1261814: Use the presence of the content global, and not any random global, to determine whether to run the close handler. r=bz
791433f9b681a4a3bce3106484352b684d76970a: Bug 1259581: Remove MOZ_MEDIA_NAVIGATOR. r=jesup
Kyle Huey <khuey@kylehuey.com> - Tue, 05 Apr 2016 20:12:03 -0700 - rev 291824
Push 74685 by khuey@mozilla.com at Wed, 06 Apr 2016 03:21:47 +0000
Bug 1259581: Remove MOZ_MEDIA_NAVIGATOR. r=jesup
496db28e275d83a8a8d57033384d18199ccbcbd9: Bug 1222889 - Ignore selection change notifications when auto-completing; r=margaret
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:54:12 -0400 - rev 291823
Push 74684 by nchen@mozilla.com at Wed, 06 Apr 2016 01:55:20 +0000
Bug 1222889 - Ignore selection change notifications when auto-completing; r=margaret Adding the auto-completion text in the URL bar triggers selection change notifications on Android 5.0 and above. That led us to think the user changed the selection, and in turn commit the auto-completion. This patch makes us ignore this edge case and preserve the auto-completion.
1f5831c61765727b3d0a975f121809aca9e766d5: Bug 1260243 - Remove sendEventToGeckoSync and related code; r=me
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:41 -0400 - rev 291822
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1260243 - Remove sendEventToGeckoSync and related code; r=me We can remove GeckoAppShell.sendEventToGeckoSync and related code because GeckoThread.waitOnGecko is replacing it.
66c977ccd22e3dcd7afe3916a4501dda20c8a14d: Bug 1260243 - Call GeckoThread.onPause/onResume in GeckoService; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:41 -0400 - rev 291821
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1260243 - Call GeckoThread.onPause/onResume in GeckoService; r=snorp Inform Gecko of the Android process lifecycle by calling GeckoThread.onPause and onResume, so that Gecko is more likely to be in a consistent state if Android kills our process.
66e21047f5419de32126167d2c318c4f4132c3ff: Bug 1260243 - Convert backgrounding/foregrounding GeckoEvent to native calls; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:41 -0400 - rev 291820
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1260243 - Convert backgrounding/foregrounding GeckoEvent to native calls; r=snorp Convert APP_BACKGROUNDING and APP_FOREGROUNDING events in GeckoEvent to native calls onPause and onResume in GeckoThread, respectively.
4c40aad4abfed90067cb1ceafc32a3337da171d9: Bug 1260243 - Add GeckoThread.waitOnGecko; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291819
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1260243 - Add GeckoThread.waitOnGecko; r=snorp GeckoThread.waitOnGecko blocks the current thread and waits for previous events on the Gecko thread to finish executing before continuing. This is implemented by synchronously running a dummy event on the Gecko thread. This patch also lets us get rid of sendEventToGeckoSync in GeckoAppShell.
4743abb7f7ff4b08c97ccfe4af06015b9207ffb5: Bug 1259653 - Update Robocop tests; r=gbrown
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291818
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1259653 - Update Robocop tests; r=gbrown This bug changed the meaning of profiles with empty names (""). It used to mean the same thing as a null name, which represents the default profile. However, the new behavior is that an empty name indicates a custom profile. So the tests involving empty names are removed from testGeckoProfile.
0e648c021a957e5bfad6d5dbe657791583de478c: Bug 1259653 - Respect the profile when starting GeckoService; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291817
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1259653 - Respect the profile when starting GeckoService; r=snorp In GeckoService, wait until we get an Intent before starting GeckoThread using the profile information contained in the Intent.
954498882fb71ee860296000279317b0a274f5b8: Bug 1259653 - Support initializing GeckoThread with a specific profile; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291816
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1259653 - Support initializing GeckoThread with a specific profile; r=snorp Add GeckoThread.initWithProfile that make it easy to target a particular profile. The method succeeds when GeckoThread has not been initialized or is already using the specified profile. It fails when the current profile does not match the specified profile.
cecaa7c35791dd866b3ff9607c77bc698c72c09e: Bug 1259653 - Make sure GeckoThread handles custom profiles; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291815
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1259653 - Make sure GeckoThread handles custom profiles; r=snorp Make sure GeckoThread adds the appropriate profile arguments even for custom profiles.
f6968de072c7b45cd61a271095d7ba5900e4070e: Bug 1259653 - Treat custom profiles differently in GeckoProfile; r=margaret
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291814
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1259653 - Treat custom profiles differently in GeckoProfile; r=margaret Make sure we treat profiles under a custom directory differently. To simplify things, custom profiles must already exist, and we don't attempt to cache instances of GeckoProfile containing custom profiles. Custom profiles are an edge use case (must be passed in via Intent arguments) so I think it's reasonable to have this behavior change.
e90c159a3b61a6160af6dd508ff3118535be97c1: Bug 1258554 - Only determine GeckoThread arguments when needed; r=snorp
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291813
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1258554 - Only determine GeckoThread arguments when needed; r=snorp Only determine GeckoThread arguments when GeckoThread has not been started in GeckoApp. Otherwise, if GeckoThread has already started, we don't need those arguments.
f695b82c6f94021b0737ca13795ba8c3a89ae9fe: Bug 1258554 - Don't touch GeckoApp from GeckoProfile; r=margaret
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291812
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1258554 - Don't touch GeckoApp from GeckoProfile; r=margaret GeckoProfile.get() was reaching into GeckoApp to get and set the current profile. I think now that GeckoThread is managing the profile, we don't need that anymore. Also move the GuestSession check to getFromArgs, and get rid of GeckoApp.getDefaultProfileName and GeckoProfile.sIsUsingCustomProfile, which are redundant now.
f3b94a9f2bd1bc271331b03fce3d544a3d11abb3: Bug 1258554 - Remove GeckoApp.mProfile; r=margaret
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:40 -0400 - rev 291811
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1258554 - Remove GeckoApp.mProfile; r=margaret GeckoApp should not be caching the current profile.
49d26e64c3167e0319b49432a9e1ffae835f5d84: Bug 1258554 - Let GeckoThread manage the active profile; r=snorp r=margaret
Jim Chen <nchen@mozilla.com> - Tue, 05 Apr 2016 21:43:39 -0400 - rev 291810
Push 74683 by nchen@mozilla.com at Wed, 06 Apr 2016 01:45:14 +0000
Bug 1258554 - Let GeckoThread manage the active profile; r=snorp r=margaret Because Gecko itself can only handle one profile per process, we should let the GeckoThread singleton manage our GeckoProfile instance on the Java side, instead of using GeckoApp.
542411a64ac407ec30e83e3db5a6cb4e12b6bf3d: Bug 1261719 - Suppress MSVC warning C4595. r=glandium
Chris Pearce <cpearce@mozilla.com> - Mon, 04 Apr 2016 10:34:22 +1200 - rev 291809
Push 74682 by cpearce@mozilla.com at Wed, 06 Apr 2016 01:10:20 +0000
Bug 1261719 - Suppress MSVC warning C4595. r=glandium C4595 is "'operator new': non-member operator new or delete functions may not be declared inline". This warning is already suppressed for newer versions of clang. MozReview-Commit-ID: GTzLtIGtpbR
296675bfe330a157e8b3054befee29273e3ac3fb: Bug 1261170 - add a single node ProcessContentInserted method version, r=yzen
Alexander Surkov <surkov.alexander@gmail.com> - Tue, 05 Apr 2016 20:48:30 -0400 - rev 291808
Push 74681 by surkov.alexander@gmail.com at Wed, 06 Apr 2016 00:48:42 +0000
Bug 1261170 - add a single node ProcessContentInserted method version, r=yzen
336759fb7df024ec7fe456df8337316e8361c4d5: Bug 933257 - Part 9: Use fdlibm in asm.js. r=luke
Tooru Fujisawa <arai_a@mac.com> - Sat, 05 Mar 2016 05:18:09 +0900 - rev 291807
Push 74680 by arai_a@mac.com at Wed, 06 Apr 2016 00:00:56 +0000
Bug 933257 - Part 9: Use fdlibm in asm.js. r=luke
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip