Firefox/Projects/Jetpack Uplift Exploration/Notes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 67: Line 67:
** Most Jetpacks don't need full iframe functionality, which is expensive for how its used
** Most Jetpacks don't need full iframe functionality, which is expensive for how its used
** Add API to add an image/button, with relevant event callbacks
** Add API to add an image/button, with relevant event callbacks
== Related Sprints ==
'''New Extension Manager API and UI'''
* https://wiki.mozilla.org/Firefox/Sprints/Extension_Manager_API
* https://wiki.mozilla.org/Extension_Manager:UI_Update
* Jetpacks would fit great as first class citizens here, alongside current addons. The new API will make that possible, and the UI will make it doable.
'''Windows Theme Revamp'''
* https://wiki.mozilla.org/Firefox/Sprints/Windows_Theme_Revamp
* This includes the possible/probable removal of the menubar and statusbar. These are the 2 most common areas for addons to extend. Even without these being removed, its clear that the browser window needs to provide more easy ways for things to be added to the UI, in areas that make sense.
'''Doorhanger notifications'''
* https://wiki.mozilla.org/Firefox/Namoroka/Doorhanger_notifications
* New UI to hook into.
Confirmed users
587

edits

Navigation menu