Jetpack/Roadmap/2013: Difference between revisions

Jetpack/Roadmap/2013 (view source)

Revision as of 01:27, 8 December 2012

1 byte removed , 8 December 2012

→‎P2 APIs

Canuckistani

Confirmed users

1,100

edits

Revision as of 01:27, 8 December 2012 (view source) Canuckistani (talk \| contribs) (→‎P1 APIs) ← Older edit		Revision as of 01:27, 8 December 2012 (view source) Canuckistani (talk \| contribs) (→‎P2 APIs) Newer edit →
Line 66:		Line 66:

	# Intercepting Network requests. Several popular developer tool add-ons rely on the low-level nsiContentPolicy interface to intercept requests and provide enhanced views of the requested content. It should be trivial for add-on developers to intercept and react to a specific class of network requests.		# Intercepting Network requests. Several popular developer tool add-ons rely on the low-level nsiContentPolicy interface to intercept requests and provide enhanced views of the requested content. It should be trivial for add-on developers to intercept and react to a specific class of network requests.

	# HTML5 Support. As the web platform gets more powerful, add-on developers should also benefit from new HTML5 apis. Previously captured in the 2011 roadmap as '[https://wiki.mozilla.org/Features/Jetpack/Make_Add-on_SDK_Hug_the_Web_Harder hug the web harder]', we feel that providing a more web-like environment is the simplest way to provide add-on developers with access to powerful apis such as Websocket, IndexedDb and various device apis.		# HTML5 Support. As the web platform gets more powerful, add-on developers should also benefit from new HTML5 apis. Previously captured in the 2011 roadmap as '[https://wiki.mozilla.org/Features/Jetpack/Make_Add-on_SDK_Hug_the_Web_Harder hug the web harder]', we feel that providing a more web-like environment is the simplest way to provide add-on developers with access to powerful apis such as Websocket, IndexedDb and various device apis.