Opened 12 years ago

#520 closed defect (Fixed)

Documents partially fail to load sometimes after Tor Toggle

Reported by: mikeperry Owned by: mikeperry
Priority: High Milestone:
Component: Applications/Torbutton Version: 1.1
Severity: Keywords:
Cc: mikeperry, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Sometimes when you load a document in one tor state, change Tor states, and then open links in new tabs
off the original document, pieces of the new tab fail to load. This is likely due to an issue in either
the window caching mechanism or the content policy itself.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Attachments (1)

torbutton-1.2.0rc5-dev.xpi (191.4 KB) - added by mikeperry 11 years ago.
This gets a major case of bug 520 for me. Does it get al cases?

Download all attachments as: .zip

Change History (7)

comment:1 Changed 12 years ago by mikeperry

Another (perhaps related, perhaps not) symptom of this is that javascript is not fully enabled
immediately after tor toggle completes. This could just be a race condition due to the asynchronous
nature of the button toggle though...

comment:2 Changed 12 years ago by keb

confirmed in 1.1.16-alpha
i have not checked "close all Tor windows and tabs on toggle" but all other items on the Dynamic Content preferences are checked.
when i start with torbutton on, open some pages, then toggle it off, the tabs stay there but the links in the pages do not work (even when attempting to open them in the same page). if i toggle torbutton back on, the links work, but the cookies are lost as expected (so i had to try twice to fill out this bug comment :D)

comment:3 Changed 12 years ago by mikeperry

That is not an instance of this bug.. Believe it or not, that is actually a feature. Because of firefox bug
409737 (https://bugzilla.mozilla.org/show_bug.cgi?id=409737) we have to block redirects and page reloads
that originate from javascript, because they can be used to unmask your original IP after tor has been
toggled. However, from the blocking code, there is no way to differentiate user clicks from javascript
fetches and redirects..

Plus, its sort of a feature in that it prevents you from accidentally clicking on links from tor loaded pages
while moving windows around ;). I have done that numerous times myself, actually. But as soon as the that
Firefox bug gets fixed, I will probably make it an option that is off by default.

Also, your Tor cookies were already lost as soon as you first toggled out of Tor, so you would have had to
log in again anyways. If you want to have your cookies there for you after toggling in and out of tor (to
click on links or what-have-you), set the option to keep both Tor and Non-Tor cookies in jars.

comment:4 Changed 11 years ago by torbert

I believe I am experiencing this. Add to parts that don't load would be links not working. Click on them and they do nothing as you would expect if I can gone from a non tor to tor state and tried a currently open page.

This seems to have got increasingly bad (for me) after 1.1.20rc1 was released. Prior to that it would be a case of every so often a page would not load fully but I could still navigate links on the page.

Problem happens on both OS X and Win XP with FF 2.0.0.14 and FF >=3rc2

Tor usage is pretty much crippled at this stage.

Changed 11 years ago by mikeperry

Attachment: torbutton-1.2.0rc5-dev.xpi added

This gets a major case of bug 520 for me. Does it get al cases?

comment:5 Changed 11 years ago by mikeperry

torbert: Are you still here? Can you try the snapshot in the attachments tab? It fixes a major case of this bug for me.

comment:6 Changed 11 years ago by mikeperry

flyspray2trac: bug closed.
I think we finally got this one. Fixed in 1.2.0rc6.

Note: See TracTickets for help on using tickets.