3rd-party-app could launch CustomTabsActivity, and could also configure
a custom action button. Now let CustomTabsActivity supports it by
creating a MenuItem.
MozReview-Commit-ID: 2KuMgBJy2gz
--HG--
extra : rebase_source : 93bcfb33001005d307dba68f898375ab7d86adb2
To support ActionButton in CustomTabsActivity, information should be
extract from intent.
MozReview-Commit-ID: 3C19U0EQfV6
--HG--
extra : rebase_source : a8d941a3fd740d5d8863e748b20de790b8bf589c
This variable is useless. So far we reference to a toolbar instance by
local variable. Removing it makes less ambiguous.
MozReview-Commit-ID: 8zrEKaB2H48
--HG--
extra : rebase_source : e35e3f87876ca497745585134018cff41536b9b0
This shouldn't ever be true - but we have crash reports from
devices running API 10 (Android 2.3), despite having a minimum
requirement of API 15 (Android 4). The cause is unknown, but could
be caused by Google Play bugs (e.g. if it were to ignore an increase
in the minimum SDK), or some other override.
MozReview-Commit-ID: 12uHsDxGPp
--HG--
extra : rebase_source : c6de3f0ed88bf506ca55297323e2670cd5641965
extra : source : 0da24048d1a8206a3a30d6b32c2d11a13cc119f6
I accidentally added this while working on a fix for Bug 1120441,
and forgot to remove it before landing. This call isn't harmful,
but it's unnecessary.
MozReview-Commit-ID: FrnhoYWFvKR
--HG--
extra : rebase_source : d5c4afef36e45bbf8ea4ef4932af55d94ac2a3a3
For components also referencing it in code, see the blockers of bug 1336311.
MozReview-Commit-ID: 4tUZ24HKBWy
--HG--
extra : rebase_source : ec16149f525b9b7eaca7f96f1369929d21497121
Let password manager handle opening the popup on username fields itself.
MozReview-Commit-ID: FbI6CgsadEd
--HG--
extra : rebase_source : b50f8ecaf5daff5660832894f083e2fda7336e3f
There appears to be a race occurring where InputExhausted callback isn't always called.
The issue could be reproduced prior all those changes, albeit rarely.
The tracking of re-enabling this feature will be done in bug 1336358
MozReview-Commit-ID: 5rPpcCcgNIq
--HG--
extra : rebase_source : bf3513e5ff8d8c72ed7aa505c8fda723a480c243
Our version of the palette support library crashes for certain icons on x86 systems.
MozReview-Commit-ID: E6eEyFXd4uK
--HG--
extra : rebase_source : fe2e3d55ff7744d480c8a6318aba09bb2c519a13
To test different situations
* Intent has custom animation
* Intent has no custom animation
MozReview-Commit-ID: 9KqBJu9x4nw
--HG--
extra : rebase_source : 30820e83d91df185cc70155bb528c4bbe9316869
3rd party app could specify its own custom-exit-animation when launching
CustomTabsActivity.
For that case, to call `overridePendingTransition` in method finish().
MozReview-Commit-ID: CivYpP2jvXp
--HG--
extra : rebase_source : 23f202a08af134f83814ac89b26a1c0d0f480478
This icon contains no arc curves, and has been tested to not display
corruption on Android 4 - we'll hopefully not run into any issues with it!
MozReview-Commit-ID: 8ISTp4i5u4O
--HG--
extra : rebase_source : 445bdaea628b9c23ac77cd6611d9438d70fbe69a
The support library on Android 4 seems have two unrelated VectorDrawable issues:
- overzealous proguarding results in drawable corruption (already fixed)
- arc curves can result in the entire drawable disappearing
This patch fixes the latter issue, by converting all remaining VectorDrawables
(some had already been fixed in a separate bug where arc curves caused corruption
on Android 6).
MozReview-Commit-ID: 2oWRXDnDZ3v
--HG--
extra : rebase_source : bd5413e304360d5ab18b95b2855f65e07a6d8a09
The return value of isKnownContent() now depends on whether we exclude this type of content or not.
This patch updates the test to reflect that.
MozReview-Commit-ID: F4KAVdv2l1X
--HG--
extra : rebase_source : 842e9f382bd7db3f3511624dd7b6a3464d114fd6
Julian_Chu
Tushar Saini (:shatur)
Wes Kocher
Andrzej Hunt
Sebastian Hengst
Jan Henning
Carsten "Tomcat" Book
Matthew Noorenberghe
Nevin Chen
Kris Maglione
Jean-Yves Avenard
maliu
Phil Ringnalda
Chris Peterson
Sebastian Kaspari
Tim Huang
Dylan Roeh
Swaroop Rao
Daniel Holbert
srivatsav
jdarcangelo
Andrea Marchesini