Bug 991167 added BundleEventListener that allow dispatching an event
directly to the UI thread or to the background thread. This patch adds
tests to testEventDispatcher, to test that the events are dispatched on
the correct threads and that the Bundle messages are correct. Because
these events are asynchronous, the test waits for each event to be
processed before continuing.
I wasn't using the wrapped drawable when setting the icon, which
curiously works on L+ devices, but not pre-L.
--HG--
extra : commitid : 9CZQGehAOIh
extra : rebase_source : 1f73a543049fa48a1e76e17b9042edb3354164d4
Note that this undoes a small change I made previously in this series to set
the color of the action bar icons via setColorFilter.
--HG--
extra : commitid : GY9G4bvX8lv
extra : rebase_source : 6b2f1407e6ffd1f4e9767f0047e9ff7220f26cf3
JNIObject is the base class for any class that wish to use per-instance
native methods. It encapsulates the long native pointer that used to be
in NativeJSContainer.
For example, these values may be used in JS only.
--HG--
extra : commitid : 3gD1zA9TIOz
extra : rebase_source : d078121ec0aedd3a3b994539c3528a323ff24da3
The use case is to ship a classes.dex file in a Gecko add-on. This
makes it easy to extract such a file from an add-on to a temporary
location. (Sadly, the Android Dex loading classes expect files, not
streams.)
--HG--
extra : commitid : 5hvLXqQHtZz
extra : rebase_source : 6d5964253c7510f02c7ff7c3889264d341b2a61a
extra : histedit_source : f22be3f7c6a12f4aafc222e954d6cbeb466fe147
Fullscreen with the modern flags requires 4.1+ now; 4.0- is using the old
flags.
--HG--
extra : rebase_source : aafbbb38566d3b6fe6cccf877c5462aaa1781cb2
A more complete solution would rework our fullscreen support to ensure the
flags are consistently used (e.g. reader mode just uses low_profile even though
ActivityUtils.setFullScreen does both low profile and fullscreen).
--HG--
extra : rebase_source : ecffff89ea2c6b6c4145626398e458623f6c773b
This is the approach we already take everywhere else we make a jar🫙 URI.
I've unified those places into GeckoJarReader, cleaned up imports, fixed a
typo, and wrote a trivial test for this case.
I made a few utility methods static to facilitate testing and future refactoring.
This is the approach we already take everywhere else we make a jar🫙 URI.
I've unified those places into GeckoJarReader, cleaned up imports, fixed a
typo, and wrote a trivial test for this case.
I made a few utility methods static to facilitate testing and future refactoring.
The constants JAR contains AppConstants and SysInfo. SysInfo depended
on HardwareUtils for one function, which can (should?) be in SysInfo
anyway, so I moved it.
Both SysInfo and AppConstants should be available to Robocop tests,
but they are compiled too early to access RobocopTarget. Since
nothing in GeckoView should know about GeckoView, I moved the
annotation to the Fennec-level proguard.cfg.
--HG--
extra : source : d2c14599cbab6c476465a6ba142c7c2501895cb3
The constants JAR contains AppConstants and SysInfo. SysInfo depended
on HardwareUtils for one function, which can (should?) be in SysInfo
anyway, so I moved it.
Both SysInfo and AppConstants should be available to Robocop tests,
but they are compiled too early to access RobocopTarget. Since
nothing in GeckoView should know about GeckoView, I moved the
annotation to the Fennec-level proguard.cfg.
--HG--
extra : rebase_source : cdba5f056a41ec28f190dd7ebf82213a358cb3a8
extra : source : d2c14599cbab6c476465a6ba142c7c2501895cb3
The constants JAR contains AppConstants and SysInfo. SysInfo depended
on HardwareUtils for one function, which can (should?) be in SysInfo
anyway, so I moved it.
Both SysInfo and AppConstants should be available to Robocop tests,
but they are compiled too early to access RobocopTarget. Since
nothing in GeckoView should know about GeckoView, I moved the
annotation to the Fennec-level proguard.cfg.
--HG--
extra : rebase_source : 6504b2324fb7534217163e21218c194df0505a75