Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-launcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-launcher
  • Issues
  • #31487
Closed
Open
Issue created Aug 22, 2019 by Mark Smith@mcs

Modify moat client code so it is compatible with ESR68

While working on legacy/trac#29430 (moved), Kathy and I found some incompatibilities in Tor Launcher's moat client code (src/modules/tl-bridgedb.jsm). All of the problems are due to Firefox internal API changes. While working on legacy/trac#31300 (moved), we did not exercise this code so we did not find these problems then.

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