[Menu Redesign] Support custom tab configurations for the new navbar
Categories
(Firefox for Android :: Toolbar, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox130 | --- | verified |
People
(Reporter: petru, Assigned: petru)
References
(Blocks 2 open bugs)
Details
Attachments
(13 files, 3 obsolete files)
1.08 MB,
video/mp4
|
Details | |
1.07 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
4.92 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
8.46 MB,
video/mp4
|
Details | |
52.39 KB,
image/jpeg
|
Details |
Based on
- https://developer.chrome.com/docs/android/custom-tabs
- https://developer.chrome.com/docs/android/custom-tabs/browser-support
a browser should support various customizations provided by the starting app.
Currently Fenix support a limited subset [1] with the new navbar getting some for free but other important ones not being supported.
Testing with dev-tabs-launcher
[2] I see the following features working/missing:
Feature | Addressbar | Navbar |
---|---|---|
Colours | ||
- choosing between ligtht/dark/system theme | ✅ | ❌ |
- choosing toolbar theme | ✅ | ❌ |
- choosing system navbars theme | ✅ | ✅ |
- change menu color | ❌ | ❌ |
- pass colour scheme to Gecko | ❌ | ❌ |
Custom buttons | ||
- custom close button | ✅ | ✅ |
- custom action button | ✅ | ✅ |
- whether to show or not the share button | ✅ | ❌ |
- custom options in the 3dot menu | ✅ | ❌ |
[1] https://searchfox.org/mozilla-central/rev/93692d0756f01f99e2b028e40b45776fa0a397e9/mobile/android/android-components/components/feature/customtabs/src/main/java/mozilla/components/feature/customtabs/CustomTabsToolbarFeature.kt#132
[2] https://github.com/ohmae/dev-tabs-launcher
Assignee | ||
Comment 1•1 year ago
•
|
||
In regards to the navbar I think we should address asap the features supported by the addressbar and not yet supported by the navbar.
Later we can look into supporting a larger set of custom tab customisations. Having two toolbars (addressbar + navbar) supporting this should allow for an improved user experience.
To note that two toolbars should've already be supported with customized colours [2], buttons [2] and gestures [3].
[1] https://developer.android.com/reference/androidx/browser/customtabs/CustomTabsIntent.Builder#setSecondaryToolbarColor(int)
[2] https://developer.android.com/reference/androidx/browser/customtabs/CustomTabsIntent.Builder#setSecondaryToolbarViews(android.widget.RemoteViews,int[],android.app.PendingIntent)
[3] https://developer.android.com/reference/androidx/browser/customtabs/CustomTabsIntent.Builder#setSecondaryToolbarSwipeUpGesture(android.app.PendingIntent)
Assignee | ||
Comment 2•1 year ago
|
||
Showing missing colours and action buttons customisations when using the new navbar.
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Comment 4•1 year ago
|
||
Since custom tabs can declare whether they want to have the share menu shown or not
we should stop showing it by default in the 3dot menu.
When custom tabs ask for the option to be shown it will be shown as an action in the
address bar.
This patch reverses the changes from bug 1899394.
Assignee | ||
Comment 5•1 year ago
|
||
Assignee | ||
Comment 6•1 year ago
|
||
Since custom tabs can declare whether they want to have the share menu shown or not
we should stop showing it by default in the 3dot menu.
When custom tabs ask for the option to be shown it will be shown as an action in the
address bar.
This patch reverses the changes from bug 1899394.
Assignee | ||
Comment 7•1 year ago
|
||
Allow these to then be used for other similar functionalities, like for how
the navbvar should look like when used for custom tabs.
Assignee | ||
Comment 8•1 year ago
|
||
Assignee | ||
Comment 9•1 year ago
|
||
Allow these to then be used for other similar functionalities, like for how
the navbvar should look like when used for custom tabs.
Assignee | ||
Comment 10•1 year ago
|
||
Assignee | ||
Comment 11•1 year ago
|
||
Allow these to then be used for other similar functionalities, like for how
the navbvar should look like when used for custom tabs.
Assignee | ||
Comment 12•1 year ago
|
||
Assignee | ||
Comment 13•1 year ago
|
||
Not sure why there are multiple of the same patches, seems like they all reference the same differential.
I'll mark some duplicates as obsoletes.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 14•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 15•1 year ago
•
|
||
Talked with Aarjav and demoed the proposed changes, 3 changes requested:
- don't allow to modify the back button icon of the custom tab, always show the "X"
- don't theme the system navigation bar, always show it as black, even when using a light theme for the app / device
- keep the share button always in the menu. It's okay if it happens to be shown in the menu and in the address bar also.
Updated•1 year ago
|
Assignee | ||
Comment 16•1 year ago
|
||
Fenix needs more control over which UI elements to be themes, specifically when
used in combination with the new navigation bar the system bars should be black.
Assignee | ||
Comment 17•1 year ago
|
||
Added a new patch with the changes Aarjav requested.
And here a recording of what the UX would look like which Aarjav approved.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 18•1 year ago
|
||
Increasing priority to P1 now that we're fixing toolbar phase 1's beta blockers.
Comment 19•11 months ago
|
||
Comment 20•11 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e2cba87dc168
https://hg.mozilla.org/mozilla-central/rev/f765bf969fcd
https://hg.mozilla.org/mozilla-central/rev/60d11d4ccb5e
https://hg.mozilla.org/mozilla-central/rev/d96f1104816f
Assignee | ||
Updated•11 months ago
|
Updated•11 months ago
|
Comment 21•11 months ago
|
||
Verified as fixed on Nightly 130.0a1 from 07/29 with Google Pixel 8 Pro (Android 14).
There are a few known issues affecting custom tabs: 1908316, 1908318, 1908661, 1908662, 1891096 but they will be handled separately.
Updated•11 months ago
|
Updated•11 months ago
|
Description
•