This allows us to use the same Java code for any native platform,
enabling a "fat" AAR.
Differential Revision: https://phabricator.services.mozilla.com/D11497
--HG--
extra : moz-landing-system : lando
This also uses idiomatic packaging of the native libraries, which
will allow easier downstream consumption of GeckoView.
Differential Revision: https://phabricator.services.mozilla.com/D10775
--HG--
extra : moz-landing-system : lando
JaCoCo chokes on default implementations in interfaces, so remove those
for now.
Differential Revision: https://phabricator.services.mozilla.com/D12607
--HG--
extra : moz-landing-system : lando
Even if the GeckoApp activity is destroyed, the user's tabs remain open as long
as the app process itself isn't killed.
Therefore, for users who aren't automatically restoring their previous session's
tabs on startup, there's no point in renaming the current session store file so
it appears under "Recently closed" instead of being automatically restored,
unless we're really doing a cold startup (and hence mIsRestoringActivity is
false).
This also better matches what we do when we *are* automatically restoring tabs:
We only do it when !mIsRestoringActivity, too.
Differential Revision: https://phabricator.services.mozilla.com/D11800
--HG--
extra : moz-landing-system : lando
The page loading indicator should be animated while it is visible.
Previously for controlling the animation the visibility state of the parent
Drawable - ShiftDrawable would be checked, which in all cases would return
true, so the animation would run indefinitely.
The patch modifies setVisible() in accordance with the Framework version of
DrawableWrapper to corectly set the visibility of both the wrapper and the
wrapped drawables so that isVisible() will now return the correct value which
will allow stopping the animation.
Differential Revision: https://phabricator.services.mozilla.com/D12552
--HG--
extra : moz-landing-system : lando
These styles and PluginHelper.js should’ve been removed back in bug 1381916.
contentPluginDisabled.png is not referenced anywhere so it is deleted together.
Differential Revision: https://phabricator.services.mozilla.com/D11701
--HG--
extra : moz-landing-system : lando
These styles and PluginHelper.js should’ve been removed back in bug 1381916.
contentPluginDisabled.png is not referenced anywhere so it is deleted together.
Differential Revision: https://phabricator.services.mozilla.com/D11701
--HG--
extra : moz-landing-system : lando
Currently, some "input" event dispatchers in our script dispatch "input" event
with UIEvent. This is completely wrong. For conforming to HTML spec, Event
is proper event. Additionally, for conforming to Input Events, InputEvent
is proper event only on <textarea> or <input> element which has a single line
editor.
For making us to maintain easier, this patch adds new API, "isInputEventTarget"
to MozEditableElement which returns true when "input" event dispatcher should
use InputEvent for the input element.
Finally, this makes some dispatchers use setUserInput() instead of
setting value and dispatching event by themselves. This also makes
us to maintain them easier.
Note that this does not touch "input" event dispatchers which dispatch events
only for chrome (such as URL bar, some pages in about: scheme) for making
this change safer as far as possible.
Differential Revision: https://phabricator.services.mozilla.com/D12247
--HG--
extra : moz-landing-system : lando
Leaving the Fennec process running after a swipe-to-kill puts Fennec in an unrecoverable state; this ensures we kill the process anytime a user swipes-to-kill Fennec and therefore lets us recover as usual.
This allows us to use the same Java code for any native platform,
enabling a "fat" AAR.
Differential Revision: https://phabricator.services.mozilla.com/D11497
--HG--
extra : moz-landing-system : lando
This also uses idiomatic packaging of the native libraries, which
will allow easier downstream consumption of GeckoView.
Differential Revision: https://phabricator.services.mozilla.com/D10775
--HG--
extra : moz-landing-system : lando
Summary:
Speculative fix.
initialize() is called by Gecko on it's background thread after it started.
The value for the "dom.audiochannel.mediaControl" preference also comes on a
background thread.
This both can end up registering the HeadSetStateReceiver while unregistering it
happens only on the main thread.
The patch tries to avoid the race condition by making sure Receiver's
registering and unregistering is done serially on the main thread.
Depends on D12032
Reviewers: JanH
Reviewed By: JanH
Subscribers: jya
Bug #: 1505685
Differential Revision: https://phabricator.services.mozilla.com/D12033
--HG--
extra : rebase_source : 11c6b6a78f310394d91b43c0d1408e341a827d85
extra : amend_source : 07cb38f0435b58462ca0329b8bd41f5d178ff4d1
Summary:
Executing SwitchBoard.loadConfig() on a background thread is the main purpose
of the AsyncConfigLoader so executing it immediately again in the same thread
is redundant.
Depends on D12031
Reviewers: JanH
Reviewed By: JanH
Bug #: 1505685
Differential Revision: https://phabricator.services.mozilla.com/D12032
--HG--
extra : amend_source : b8ab5400e4b0afffc918754cc2e39141c331adcf
Summary:
Speculative fix for avoiding the situation in which the initialization of Mma
and registering of the PackageAddedReceiver continues on the background thread
after BrowserApp is destroyed and calls for unregistering the receiver.
By registering the receiver on the main thread we have the benefit of
sequentially execution which would guarantee that the registration is done
before trying to unregister it.
Reviewers: JanH
Reviewed By: JanH
Bug #: 1505685
Differential Revision: https://phabricator.services.mozilla.com/D12031
--HG--
extra : rebase_source : 2f0512cc269b7e6d2ee825cc82bfcdc6f6ad00d6
extra : amend_source : eb979af1cd6fe567ab3fe7213c7f631d68d9c255
