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

 
(2 intermediate revisions by one other user not shown)
Line 30: Line 30:
== Subscription / Installation / Management ==
== Subscription / Installation / Management ==


* Management through Extension Manager [[Firefox/Projects/Extension_Manager_API|API]] and [[Extension_Manager:UI_Update|UI]]
* Management through Extension Manager [[Firefox/Projects/Extension_Manager_API|API]] and [[[[Firefox/Projects/Extension_Manager_Redesign|Extension Manager Redesign]]
* Install & update comparable to current addons
* Install & update comparable to current addons


Line 64: Line 64:
* Object.freeze()
* Object.freeze()
** {{bug|492844}} - ES5: Implement Object.freeze, Object.isFrozen
** {{bug|492844}} - ES5: Implement Object.freeze, Object.isFrozen
* ChromeObjectWrapper (landed on trunk)


=== Layout ===
=== Layout ===
Line 72: Line 73:
* Lightweight iframes? Need some efficient way of sandboxing and displaying untrusted markup/code.
* Lightweight iframes? Need some efficient way of sandboxing and displaying untrusted markup/code.
* Scriptable HTML parser (@mozilla.org/xmlextras/domparser;1 only handles XML)
* Scriptable HTML parser (@mozilla.org/xmlextras/domparser;1 only handles XML)
=== Utility Libraries ===
'''Note:''' Not specific to Jetpack.
Provide utility libraries similar to FUEL but for non-browser stuff. For browser-related functions, FUEL can be expanded.
Examples:
* OAuth
* Logging
* More convenience wrappers around commonly used XPCOM components.
=== Native support for Content Scripts ===
Content scripts are JS scripts that run in content, but are provided by the browser, rather than by the website. This could be a potential first step in providing developers with native open-web tools to extend the browser. Currently this is provided by addons ([https://addons.mozilla.org/firefox/748/ Greasemonkey], and [[Labs/Jetpack/JEP/17|Jetpack has it planned]]). A technical exploration was done to see how Firefox could support this natively.
'''Requirements'''
* First-class support for content scripts
* Must be secure - content space only, no chrome privileges
'''Technical exploration'''
* Success
** But needs support from new Extension Manager
* Would work as both a standalone feature, and a platform for Jetpack (and other addons)
'''Outcome'''
* Technically sound, but need more discussion with Jetpack team


== Jetpack requirements ==
== Jetpack requirements ==
Confirmed users
954

edits