The native translator is a great feature, but its current UI placement creates an inconsistency with other core browser actions.
1. Consistency with existing patterns
Core actions like "Reload", "Bookmark", "Back/Forward" follow a consistent pattern:
They are available in the context menu AND as customizable toolbar buttons.
Users can pin, move, or hide them via "Customize Toolbar".
The translator should follow this same pattern. If it's a first-class browser feature, it deserves first-class UI integration.
2. UX efficiency for power users
Translating selected text is a frequent action. Current flow:
Select text → Right-click → Find "Translate" → Click (4 steps, precise mouse positioning).
Proposed flow with toolbar button:
Select text → Click toolbar icon (2 steps, no menu navigation).
This matches the efficiency of other core actions and respects user workflow preferences.
3. Technical feasibility
The infrastructure for customizable toolbar buttons already exists (Customize Mode, widget-areas). This would require:
Registering the translator widget as a customizable item.
Exposing a browser.translations.translateSelection() API for extensions (optional, but useful).
Request:
Please make the native translator widget:
Available in "Customize Toolbar" palette.
Movable/pinnable like other native buttons.
(Optional) Expose a command API for extension integration.
This would align the translator with Firefox's existing UI patterns and improve accessibility for power users.