Document requirements for interaction between extensions and CustomizableUI (CUI)
Categories
(WebExtensions :: General, task, P3)
Tracking
(Not tracked)
People
(Reporter: robwu, Unassigned, NeedInfo)
References
Details
In bug 1839948, particularly the discussion starting from https://bugzilla.mozilla.org/show_bug.cgi?id=1839948#c7 until https://bugzilla.mozilla.org/show_bug.cgi?id=1839948#c12, it became apparent that the expected behavior of extension button integration in the CUI (CustomizableUI) is unclear.
For example, comment 8 expressed the understanding that extension button would never be pinned by default at install,
and in comment 9 I clarified that this is not the case (i.e. extension buttons can be pinned at install time).
If the expectations are documented more clearly, then it would be more feasible to avoid storing stale information in the storage (browser.uiCustomization.state pref or XULStore) by the CustomizableUI module.
|
Reporter | |
Comment 1•1 year ago
|
||
Me to follow up after the current 120 cycle.
Description
•