Confirmed users
764
edits
Labs/Jetpack/JEP/14: Difference between revisions
Jump to navigation
Jump to search
m
→Proposal
(Added support for replacing context menu: dynamic access callback returns a menu.) |
m (→Proposal) |
||
| Line 23: | Line 23: | ||
Menus are a good example of how these tensions are exposed. Should Jetpack allow developers to modify any menu within Firefox? Only certain menus? Should Jetpack features be quarantined to submenus? Should it be clear that Jetpack menus are not part of the standard browser? What about the context menu? Should Jetpack provide preferences that default to something reasonable but give the user ultimate control? | Menus are a good example of how these tensions are exposed. Should Jetpack allow developers to modify any menu within Firefox? Only certain menus? Should Jetpack features be quarantined to submenus? Should it be clear that Jetpack menus are not part of the standard browser? What about the context menu? Should Jetpack provide preferences that default to something reasonable but give the user ultimate control? | ||
Given that Jetpack is a prototype and that one | Given that Jetpack is a prototype and that one of its goals is to maximize developer generativity, this API errs on the sides of the developer and usefulness. We'll let the Firefox team worry about these questions if and when Jetpack is uplifted. | ||
The menu API lives at <code>jetpack.menu</code>. It provides access to all the menus of the browser's menubar and context menus. | The menu API lives at <code>jetpack.menu</code>. It provides access to all the menus of the browser's menubar and context menus. | ||