#17248: Investigate new WebExtensions API requirements for our extensions --------------------------------------+-------------------------- Reporter: gk | Owner: tbb-team Type: task | Status: closed Priority: High | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: fixed Keywords: TorBrowserTeam201512 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------+--------------------------
Comment (by cypherpunks): > we don't _have_ to do anything. We don't _have_ to port these to WebExtensions, as 'legacy' add-ons will live on Except that they'll start ripping out XUL/XPCOM in its entirety, and making other backwards-incompatible changes with no worries, since only Mozilla-written code is intended to use those APIs from now on anyway. There's going to be some required porting of some kind, it might as well be to the supported stable API. In particular, if there's any stored data the add-on uses, you definitely want to move to an 'embedded WebExtension' https://developer.mozilla.org /en-US/Add-ons/WebExtensions/Embedded_WebExtensions architecture and use webext APIs for stored data sooner than later to ease any future migration, like if the legacy APIs used for data storage in e.g. Firefox 52 are suddenly not there in Firefox 59. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17248#comment:19> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs