Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5073

Closed
Open
Created Feb 10, 2012 by cypherpunks@cypherpunks

torbutton breaks leechblock extension

The leechblock extension < http://www.proginosko.com/leechblock.html > to Firefox allows the user block access to certain sites during certain times of the day, in order to reduce the temptation for time-wasting. It seems to interact badly with torbutton; it fails to enforce the blocking time periods correctly; blocking tends to start and end several hours early/late.

I think the problem is that leechblock relies on the javascript Date object to report the current local time correctly; AFAICT torbutton wraps this and forces it to report GMT instead. Leechblock gets additionally confused as the local time reported by the Date object changes whenever torbutton is toggled.

Is it possible for torbutton to wrap the Date object in such a way that it reports GMT as local time to javascript code running on web pages, and the correct local time to firefox extensions?

Tested using Leechblock version 0.5.2, and the versions of Firefox and Torbutton packaged with Debian squeeze (i.e. a patched Firefox 3.5.16 and Torbutton 1.2.5)

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