feat: Enable original extensions panel on hide-unified-extensions-button: false
Summary
-
Updated
ZenSiteDataPanel.sys.mjsto support multiple panels and pass relevant objects tobrowser-addons.js -
Patched
browser-addons.jsto accept panel objects -
Patched
navigator-toolbox.jsto get panel objects fromwindow.gZenSiteDataPanel -
Updated
zen-single-components.cssto conditionally hide extensions on unified panel
Screenshots
-
hide-unified-extensions-button: true -
hide-unified-extensions-button: false
Notes
- Toggling
hide-unified-extensions-buttondoes require a browser restart to fully take effect and swich over. This is because the list of extensions are added on browser initialization. It does not appearbrowser/components/customizableui/CustomizableUI.sys.mjsis able to natively support adding and removing extensions from multiple areas
Instead of choosing what panel should be used every time, we could just revert these changes if the preference is off: ... Or at least simply override it? gUnifiedExtensions._panel = ...
Yes, that's true. Effectively that's what setMainPanel was for, but that approach is cleaner. And we can safely remove the patches on get panel() which is a nice side effect
Let me know once its finished for review @blakegearin
Please run npm run lint:fix as well and patches seems to fail importing? https://github.com/zen-browser/desktop/actions/runs/19818358014/job/56774645713?pr=11335
@mr-cheffy Thanks. Should be good to go.
Sorry for the delay, i'll review ASAP when im free
No worries. Got the conflict resolved.
https://github.com/user-attachments/assets/6f3bf13c-5c36-4d4f-a8a6-da73c49001ff
@blakegearin everything seems good, theres this issue that when opening, it opens it ontop of the button though
@blakegearin everything seems good, theres this issue that when opening, it opens it ontop of the button though
Good catch. Thankfully it was a pretty easy fix.