I'm a little concerned that this will hide other bugs but it's pretty
complicated to track down without an STR (e.g. what are all the possible ways
we load the HomePager with TopSites as the default and swap in new highlights?
How about unloading? When is onSizeChanged called?) so I don't think it's worth
investigating further.
MozReview-Commit-ID: 6OuFJ2iQsdL
--HG--
extra : rebase_source : 576e29298f131870fed987793663de499285ab1d
In the frontend we need to know if XUL buttons in the toolbar were
triggered by a touch event, so we're passing on the inputSource
in the command event.
MozReview-Commit-ID: DMvgZULk9hT
--HG--
extra : rebase_source : c455c8ec77e439bf02c1e3e8d34a36e1fb5e3bd0
The nexus.xml included in this patch is the result of starting Nexus
and manually adding the jcenter proxy repository using the Nexus web
administration interface (all in a Docker container). I know of no
way to do this configuration incrementally without the web interface.
The diff between new and the default generated configuration is a
single new <repository>..</repository> element.
MozReview-Commit-ID: 2Bg5qX41pHB
--HG--
extra : rebase_source : c945acabcedd98439a0ca0e26251bab1a41de197
extra : source : 9b794a7fc266da1ae81afd795f91e72d04bbc992
There are some situations where spans are not properly synced from
current text to shadow text. This patch takes more steps to make sure
spans are synchronized.
MozReview-Commit-ID: 1xhsJllE7Ro
--HG--
extra : rebase_source : 743828adfe9dfda93480a5372697989a77492d52
I verified the behavior is the same by replacing StringUtils.join with
TextUtils.join in the StringUtils.join test (which passed) before deleting it
all.
MozReview-Commit-ID: 1pmSdTuG0LU
--HG--
extra : rebase_source : 5d596b28f27f540a6ac57217b9e134e267e823e7
extra : source : 9cdc0fcca44abc8f2ec1ea8f853ca31f8d59ce10
The implementation of magnifying glass is changed from ImageView to ImageButton which causes to this gray background.
To keep it have same visual, we have to configure it with transparent background.
MozReview-Commit-ID: 33zYpylOzsC
--HG--
extra : rebase_source : a3d8ff4d00243e1c12465b8f67ccba337d62f34c
flush() invalidates all buffers so buffer callbacks emitted earlier than that should not proceed when they're executed after.
MozReview-Commit-ID: 3KjCmW2VwTy
--HG--
extra : rebase_source : 11ea4f017e3add355f70762f8f43f82829f9ccd2
We already have logo icons in different branding folders, the following 4 icons are redundant and
should be removed to prevent increasing APK size.
- australis/res/drawable-hdpi/firefox_logo.png
- australis/res/drawable-xhdpi/firefox_logo.png
- australis/res/drawable-xxhdpi/firefox_logo.png
- australis/res/drawable-xxxhdpi/firefox_logo.png
MozReview-Commit-ID: COWXJsYrAVE
--HG--
extra : rebase_source : 792c3406a906985fca142674a63498b8a5ea44fd
Add a sample implementation of PermissionDelegate for geckoview_example;
Because the prompt code has some existing boilerplate, the actual
prompts are implemented in BasicGeckoViewPrompt.
MozReview-Commit-ID: EDfmRPn4cjR
--HG--
extra : rebase_source : 3b4b770c606a9be3326bca3acd87770c5f8bb4fa
Add PermissionDelegate interface and implement support for Android and
content permissions (WebRTC permissions will be implemented later).
MozReview-Commit-ID: 1B2DUjh8Ajw
--HG--
extra : rebase_source : 7c0a4489b136100ca57740512436bb8cccc62f3a
Add GeckoViewPermission.js, which is responsible for handling requests
from Gecko for permissions, and passing those requests to GeckoView.
MozReview-Commit-ID: C0g24hKEYbf
--HG--
extra : rebase_source : fe949fde01ddba207b12f2bd49e52ea2bc8b8c5e
For a lot of GeckoView content process code, we send a message from
content to chrome, using a message manager, only to forward the message
to Java as an event, using an event dispatcher. This patch gives
Messaging.jsm the ability to be used in content process directly, and
lets events transparently pass through to Java.
MozReview-Commit-ID: 15dKKpQCXqJ
--HG--
extra : rebase_source : 3ab93052de3676244843c55c50ae5ade63ab8f11