WebExtensions/Future: Difference between revisions

list of addons, priorities
(uservoice link)
(list of addons, priorities)
Line 3: Line 3:
Please see the [https://webextensions.uservoice.com/forums/315663-webextension-api-ideas uservoice page] for requests from developers.
Please see the [https://webextensions.uservoice.com/forums/315663-webextension-api-ideas uservoice page] for requests from developers.


== Standard APIs ==
One of the goals here is to open up new possibilities for extensions. We want to create the sort of vibrant new community that has formed around Atom packages.
 
== Interesting Add-ons ==
 
* Tree Style Tab
* NoScript
* Vimperator/Pentadactyl
* Tab Mix Plus
* FireGestures
* Classic theme restorer
* DownThemAll
* CCK
* Easy DragToGo
 
== Priorities ==
 
* Extensions shouldn't randomly break due to small changes in the browser
* Two extensions should compose well (i.e., not break when both are installed)
* Users should always be aware when an extension is modifying the UI
* Ideally, APIs should make sense in all browsers, not just Firefox
* APIs should be easy to use
 
== Additional APIs ==


These APIs would work just like other WebExtension APIs.
These APIs would work just like other WebExtension APIs.
Line 13: Line 35:
* Ability to add tabs to about:addons.
* Ability to add tabs to about:addons.
* Ability to take images of frames/tabs (like canvas.drawWindow)
* Ability to take images of frames/tabs (like canvas.drawWindow)
* Ability to overlay the entire browser window with some HTML (which might be partially transparent).
* Change tab colors, set badges for tabs.


== Extension Points ==
== Extension Points ==
Confirmed users
130

edits