Closed
Bug 1306820
Opened 8 years ago
Closed 8 years ago
[Omnibox] Add a UI indicator to the navigation bar when a magic word is active.
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1267810
People
(Reporter: mattw, Unassigned)
Details
(Whiteboard: [omnibox]triaged)
Attachments
(1 file)
(deleted),
image/png
|
Details |
When a magic word that has been registered by an extension is active (i.e. it is typed into the navigation bar) we should make this clear in the UI so users know that the extension is now in partial control of the search suggestions and behavior.
Chrome does this by replacing its search icon with the default extension icon and the magic word with the name of the extension.
We could do something similar by replacing the identity icon with the default extension icon and replacing the magic word with the extension title similar to how "Switch to tab:" is displayed when a switch-to-tab suggestion is highlighted.
Comment 1•8 years ago
|
||
I'm thinking that the (In reply to Matthew Wein [:K-9, :mattw] from comment #0)
> Chrome does this by replacing its search icon with the default extension
> icon and the magic word with the name of the extension.
I have minor concern about spoofing opportunities here for things that might be confused with security identifiers, or well "Firefox" (which shouldn't happen) and other stuff. I'm wondering if just "Extension" might work.
Reporter | ||
Comment 2•8 years ago
|
||
This is an image of how the UI looks in Chrome for reference.
Reporter | ||
Comment 3•8 years ago
|
||
(In reply to Andy McKay [:andym] from comment #1)
> I'm thinking that the (In reply to Matthew Wein [:K-9, :mattw] from comment
> #0)
> > Chrome does this by replacing its search icon with the default extension
> > icon and the magic word with the name of the extension.
>
> I have minor concern about spoofing opportunities here for things that might
> be confused with security identifiers, or well "Firefox" (which shouldn't
> happen) and other stuff. I'm wondering if just "Extension" might work.
Yeah, that's a good point. I'll use "Extension: " and then see if UX approves.
I'm going to continue working on this as part of bug 1267810.
Comment 4•8 years ago
|
||
Per bug 1266012 I suggest we call it Add-on, or at least stay consistent between the two issues.
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•