Migrate extension widgets in the palette and overflow menu to the ADDONS area, and add rules to prevent them from going back
Categories
(Firefox :: Toolbars and Customization, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox109 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(5 files)
Once we introduce the ADDONS area, with the Unified Extensions UI enabled, the spec calls for extension widgets to only be able to exist in either toolbars or the ADDONS area. We want to prevent them from existing or being moved to the palette or the overflow menu.
This will involve adding some logic at the beginning of CUI initialization that:
- Identifies any extension widgets in the palette and moves them to the bottom of the ADDONS area
- Takes any extension widgets in the overflow panel and moves them to the top of the ADDONS area in the same order.
- Adds rules to
canWidgetMoveToArea
which prevents the extension widgets from going to the palette or the overflow menu. - Adds tests for the above.
Bonus:
5. In the event that the Unified Extension pref is turned off again, we should move all extension budgets from the ADDONS area into the overflow panel. Yes, that'll include the items that had been in the palette. This isn't a usecase that we're going to support in the long run, but what we don't want to happen is that we're backed into a corner where disabling the Unified Extensions UI in an emergency situation during rollout results in people losing their addon buttons. This will need testing as well.
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
•
|
||
In terms of timing for this work, I'd definitely like to aim it for the very beginning of the 109 cycle. My goal is to have this work written, reviewed and rigorously tested before it lands on the first day of the 109 cycle.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Another thing to test is the "reset" behaviour. When resetting, all browser action buttons should move to the addons panel.
Assignee | ||
Comment 3•2 years ago
|
||
This isn't a migration just yet. I'm following the same technique that we seemed to follow
when we first introduced the original overflow menu (see bug 1354117) - I'm going to add
a function to do the migration here, with a mechanism for (somewhat) reversing the
migration if the preference gets flipped back to false at some point.
There is no expectation that this preference will be flipped back to false - it's more of
a safety mechanism. Once we're confident that the routine in the function properly moves
items to right places, we can convert it to a proper migration so that it only runs
once on startup for folks who upgrade.
Depends on D161721
Assignee | ||
Comment 4•2 years ago
|
||
Depends on D161839
Assignee | ||
Comment 5•2 years ago
|
||
Depends on D161840
Assignee | ||
Comment 6•2 years ago
|
||
Depends on D161841
Assignee | ||
Comment 7•2 years ago
|
||
Depends on D161842
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/372c43168f40
https://hg.mozilla.org/mozilla-central/rev/7be99ada0759
https://hg.mozilla.org/mozilla-central/rev/d7031981a11d
https://hg.mozilla.org/mozilla-central/rev/7ce899ab5fd5
https://hg.mozilla.org/mozilla-central/rev/765bd4c601ff
Description
•