Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 682
    • Issues 682
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #40069
Closed
Open
Created Aug 01, 2020 by Alex Catarineu@acat

Add helpers for message passing with extensions

In Tor Browser, we need to communicate with NoScript and HTTPSEverywhere extensions via message passing. Currently, we do it in a way that the background script of those extensions will receive the message via browser.runtime.onMessage as if those messages came from some page of the same webextension.

In https://bugzilla.mozilla.org/show_bug.cgi?id=1583484 (79) the underlying message passing mechanism changed, which means we need to fix our code too. I think it's a good opportunity to refactor the code into a single place that is used both for noscript (torbutton) and https-everywhere (onion alias patch) message passing.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking