New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 865765 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Task



Sign in to add a comment

Refactor infobars to better suit Chrome on Android's growing needs

Project Member Reported by mdjones@chromium.org, Jul 19

Issue description

Chrome on Android has an ever growing list of requirements for UI at the bottom of the screen. We should build a more generic "infobar" system that supports the following:

- Persistent infobars across tabs ("app-level").
- Formal prioritization; when other infobars claim to be more important than ones already showing.
- More freedom for feature teams to customize.

On the technical side, we have the following goals:
- Build an easily extensible system.
- Remove dependence on native; at least for creating a new infobar. Currently there is tremendous overhead in creating a new infobar.
- Build a system that allows new infobars and old to exist simultaneously (as some don't have a conversion path).

This bug serves as tracking for the work associated with this task.
 

Sign in to add a comment