Open
Bug 1362741
Opened 8 years ago
Updated 2 years ago
Allow setting a browseraction label different from its title
Categories
(WebExtensions :: Frontend, enhancement, P5)
WebExtensions
Frontend
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: nico, Unassigned)
References
Details
(Whiteboard: [design-decision-approved] triaged)
Attachments
(1 file)
Webextension browseraction buttons should have a label in addition to the existing title, to be displayed when the button is moved from the toolbar to the "hamburger" menu.
Currently, if a browseraction button is placed in the menu, both its label and title are populated from the "default_title" manifest entry. However the title can be too long to be displayed as a label.
As a comparison, Firefox UI buttons get a different title and label, eg. the downloads button has:
- "Display the progress of ongoing downloads (%S)" as tooltip (displayed when the button is in the toolbar or menu)
- "Downloads" as label (displayed when the button is in the menu).
Updated•7 years ago
|
Whiteboard: [design-decision-needed] triaged
Comment 1•7 years ago
|
||
Hi Nicolas, this has been added to the agenda for June 20 WebExtension APIs triage meeting. Would you be able to join us?
Wiki: https://wiki.mozilla.org/Add-ons/Contribute/Triage#Next_Meeting
Agenda: https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit#
Reporter | ||
Comment 2•7 years ago
|
||
Thank you for the invitation. I am unsure I'll be able to join, however I attach a screenshot to make sure what I consider an issue is clear.
It compares what Firefox buttons have (a long, informative title + a much shorter label) to the WebExtension developer's dilemna: either a good label that will be useless as a title, or a good title that will be too long to be a good label.
Updated•7 years ago
|
Priority: -- → P5
Whiteboard: [design-decision-needed] triaged → [design-decision-approved] triaged
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•