canmove, Confirmed users
1,537
edits
Features/Jetpack/Add-onTab-API: Difference between revisions
Jump to navigation
Jump to search
Features/Jetpack/Add-onTab-API (view source)
Revision as of 22:09, 11 January 2012
, 11 January 2012no edit summary
(Created page with "{{FeatureStatus |Feature name=Feature name here |Feature stage=Planning |Feature status=In progress |Feature version=Add-on SDK 1.5 |Feature health=OK }} {{FeatureTeam |Feature p...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name= | |Feature name=Add-On Tab API | ||
|Feature stage=Planning | |Feature stage=Planning | ||
|Feature status=In progress | |Feature status=In progress | ||
| Line 11: | Line 11: | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=This API should give add-on developers the opportunity to have their add-on create a new tab with a reduced-chrome view and the ability to add html content to the tab. | |Feature overview=This API should give add-on developers the opportunity to have their add-on create a new tab with a reduced-chrome view and the ability to add html content to the tab. | ||
|Feature users and use cases=The best example of an add-on tab is the about:addons page. This page, when launched will take away the chrome for the awesomebar/search as well as a visible bookmarks bar leaving the user with a special page where the content is the most important element. This can be useful for preferences and special content. | |Feature users and use cases=The best example of an add-on tab is the about:addons page. This page, when launched will take away the chrome for the awesomebar/search as well as a visible bookmarks bar leaving the user with a special page where the content is the most important element. This can be useful for preferences and special content. | ||
|Feature implementation plan=The implementation of this API should be fairly straight-forward as the page content implementation should be similar, if not the same, as the content allowed in currently in a panel. Therefore, new implementation should just be the creation of a new tab, and the creation of the reduced-chrome interface for that tab. | |Feature implementation plan=The implementation of this API should be fairly straight-forward as the page content implementation should be similar, if not the same, as the content allowed in currently in a panel. Therefore, new implementation should just be the creation of a new tab, and the creation of the reduced-chrome interface for that tab. | ||
}} | }} | ||