[tbb-bugs] #17248 [Applications/Tor Browser]: Investigate new WebExtensions API requirements for our extensions

[Tor Bug Tracker & Wiki]

#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 mcs):

 Replying to [comment:12 tom]:
 > I think that https://developer.mozilla.org/en-US/Add-
 ons/WebExtensions/API/Runtime/connectNative might be a workable solution
 to this one. Obviously it would require the other side (Tor's control
 port) to change.

 I think we should leave tor unchanged and instead think about splitting
 Tor Launcher into a WebExtensions (JavaScript) part and a compiled (Go?)
 "shim." Communication between the two pieces would be via Native messaging
 (aka connectNative). Kathy and I did something similar for a Chrome
 extension that we wrote several years ago (a non-Tor project). It worked
 pretty well. Obviously we will need to define our own protocol between the
 JS code and the compiled code.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17248#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online