Open Bug 1810162 Opened 1 year ago Updated 6 months ago

Add support for EXTRA_REMOTEVIEWS (secondary toolbar) in Custom Tabs feature

Categories

(Fenix :: Tabs, enhancement, P3)

Product:
Fenix
Component:
Tabs
Platform:
All
Android
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: jonalmeida, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid])

Some of our adjacent app teams (Pocket) want to make use of secondary toolbar views in Custom Tabs. It would be a good idea if we had support for this API in our browser as well so that users who have Fenix are able to get the full experience.

Today, not handling the new API has no direct consequence on the user apart from not having the full experience that a third party app had originally intended.

Concerns:

  1. Consider how does the remote view work when our toolbar is at the bottom.
  2. What happens with bottom-anchored content?
  3. How do we handle scrolling when the toolbar disappears? (See what Chrome does.)
  4. Consider max height for the remote views to avoid blocking web content. (See what Chrome does.)

S3 because this doesn't block core functionality despite it being an API we don't support (even though this is marked as an enhancement).

Severity: -- → S3
Severity: S3 → N/A
Priority: -- → P3

Removing off the sprint tracking for now; we can pick this up when we want to work on the custom-tabs-refresh.

Whiteboard: [geckoview:m112?]
Whiteboard: [fxdroid]
You need to log in before you can comment on or make changes to this bug.