Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,004
    • Issues 1,004
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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 Browser
  • Issues
  • #16633
Closed
Open
Created Jul 22, 2015 by Mike Perry@mikeperryDeveloper

Enable and isolate Firefox connection prediction

In legacy/trac#16625 (moved), we found that Firefox's network prediction was partially disabled due to our use of SOCKS proxy settings, and also that it wasn't properly getting isolated in the cache or elsewhere.

We should try to enable this, though, as it will likely represent a significant decrease in page load times. If we enable isolation, the only real privacy issue is prediction for link hover, and that can be easily disabled in Predictor::PredictForLink() (there already is a check to disable it for HTTPS links).

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