Just a note for others to keep in mind while having this discussion. We should be taking into consideration lessons learned from desktop add-ons (for instance, compatibility/perf issues) and mobile Firefox add-ons (similar to the proposal below).
If our final vision for Firefox OS add-ons allows them to run system wide, we'll also need to implement a blocklisting mechanism (preferably with more controls than we have on the desktop) for malicious add-ons. Security needs to be a concern. -Alex On Jul 9, 2013, at 12:07 AM, Fabrice Desre <[email protected]> wrote: > Hi all, > > Another item on the "Engineering whislist" that I think is crucial for > b2g success is to add some kind of add-on support. Firefox's popularity > is in no small part due to its add-on model that allows both > customization and extensibility. > > How can we translate this model to make b2g even better? > > First, we need to use web applications as add-ons and not reuse the xpi > format from firefox, since it's designed for other cases. > > Secondly, there's the big question of which kind of functionality we > want to offer to add-ons. We very likely need at least themeing support > (maybe even support styles from userstyles.org) and page scripts (like > scriptish/greasemonkey). If we want to allow resources filters (for ad > blockers for instance) this may be harder, but also really interesting! > > Add-ons being applications, their api access will be similar to > applications - no chrome privileges, etc. > > Thoughts? > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
