#24190 closed defect (worksforme)

Twitter not working on 7.0.8, and older versions!

Reported by: rebbecca Owned by: tbb-team
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Twitter is not working in 7.0.8 tor browser on High Security Level.
incomplete loading.
no problem in the Medium Level.

Child Tickets

Change History (14)

comment:1 Changed 22 months ago by Dbryrtfbcbhgf

Here is a excerb  from twitter's site.

Twitter.com makes heavy use of JavaScript

If you cannot enable it in your browser's preferences, you may have a better experience on our mobile site.

When you set the security slider to high javascript is disabled for every site, you can enable javascript on specifically Twitter by.

  1. click on no script icon in the upper left or right.

2.click options and click whitelist.

3.in the address field add https://twitter.com/ and click OK.

Last edited 22 months ago by Dbryrtfbcbhgf (previous) (diff)

comment:2 Changed 22 months ago by rebbecca

No!
I meant even when twitter.com is white listed the problem will be there.
this is a "new problem" and has been occurred after the recent update.
before that twitter loaded with no problem in High Security Level when it was allowed in Noscript; unlike now.

comment:3 in reply to:  2 Changed 22 months ago by Dbryrtfbcbhgf

Replying to rebbecca:

No!
I meant even when twitter.com is white listed the problem will be there.
this is a "new problem" and has been occurred after the recent update.
before that twitter loaded with no problem in High Security Level when it was allowed in Noscript; unlike now.

What URL's are not loading correctly, because the login page works fine.

comment:4 Changed 22 months ago by rebbecca

please check this problem in twitter after logging in.
In High Security Level, JavaScript can't loaded in twitter.com even if the site is in NoScript white list.
the problem will be solved only if you choose medium security level.

Last edited 22 months ago by rebbecca (previous) (diff)

comment:5 in reply to:  4 ; Changed 22 months ago by gk

Status: newneeds_information

Replying to rebbecca:

please check this problem in twitter after logging in.
In High Security Level, JavaScript can't loaded in twitter.com even if the site is in NoScript white list.
the problem will be solved only if you choose medium security level.

Chances are that NoScript is actually doing that. Could you try figuring that out starting with (older) clean, new Tor Browser versions? You'll find them at https://archive.torproject.org/tor-package-archive/torbrowser/

You can update NoScript manually on about:addons right-click on NoScript -> Find Updates

comment:6 in reply to:  5 ; Changed 22 months ago by rebbecca

Replying to gk:

Chances are that NoScript is actually doing that. Could you try figuring that out starting with (older) clean, new Tor Browser versions? You'll find them at https://archive.torproject.org/tor-package-archive/torbrowser/

You can update NoScript manually on about:addons right-click on NoScript -> Find Updates

yes sure.
I tried two older versions from 6 and 5 Tor Browsers with non-updated NoScripts, but the issue still is there! it happened even if "Allow Scripts Globally" is selected on High Security Level.
in all situations, only choosing "Medium Security Level" could solve the issue.

Last edited 22 months ago by rebbecca (previous) (diff)

comment:7 Changed 22 months ago by rebbecca

Status: needs_informationnew
Summary: Twitter not working on 7.0.8Twitter not working on 7.0.8, and older versions!

comment:8 Changed 22 months ago by rebbecca

Priority: HighVery High

comment:9 in reply to:  6 ; Changed 22 months ago by gk

Status: newneeds_information

Replying to rebbecca:

Replying to gk:

Chances are that NoScript is actually doing that. Could you try figuring that out starting with (older) clean, new Tor Browser versions? You'll find them at https://archive.torproject.org/tor-package-archive/torbrowser/

You can update NoScript manually on about:addons right-click on NoScript -> Find Updates

yes sure.
I tried two older versions from 6 and 5 Tor Browsers with non-updated NoScripts, but the issue still is there! it happened even if "Allow Scripts Globally" is selected on High Security Level.
in all situations, only choosing "Medium Security Level" could solve the issue.

So, this worked for you in the past? If so, could you find out which the first version is that breaks (using the packages in our archive (see link in my previous comment))?

comment:10 in reply to:  9 Changed 22 months ago by rebbecca

Replying to gk:

Replying to rebbecca:

Replying to gk:

Chances are that NoScript is actually doing that. Could you try figuring that out starting with (older) clean, new Tor Browser versions? You'll find them at https://archive.torproject.org/tor-package-archive/torbrowser/

You can update NoScript manually on about:addons right-click on NoScript -> Find Updates

yes sure.
I tried two older versions from 6 and 5 Tor Browsers with non-updated NoScripts, but the issue still is there! it happened even if "Allow Scripts Globally" is selected on High Security Level.
in all situations, only choosing "Medium Security Level" could solve the issue.

So, this worked for you in the past? If so, could you find out which the first version is that breaks (using the packages in our archive (see link in my previous comment))?

but all previous versions of tor browser worked perfectly with twitter in High Security Level when twitter.com was allowed in NoScript.
but recently, several days ago after logging in twitter I see the page has not JavaScript loaded. It seems first to me, updating tor to 7.0.8 caused the problem but now after checking some older versions I wonder that the problem is repeating there.
Is it possible a probable new code changing from twitter.com has been conflicted with some tor operations?
and could you please check a twitter account in a High Security Leveled tor browser, for double check of this issue?
thanks

Last edited 22 months ago by rebbecca (previous) (diff)

comment:11 Changed 22 months ago by ln5

This seems to be a change with how Twitter uses SVG and not related to a change in Tor Browser.

Setting svg.in-content.enabled = false makes Twitter web work as expected again in my Tor Browser 7.5a7, even on security level high.

Thanks to GeKo for helping out with this.

comment:12 in reply to:  11 ; Changed 22 months ago by ln5

Replying to ln5:

Setting svg.in-content.enabled = false makes Twitter web work as expected again in my Tor Browser 7.5a7, even on security level high.

That came out wrong. s/false/true/1, so what I meant to say was:

Setting svg.in-content.enabled = true makes Twitter web work as expected
                                 ^^^^

Sorry about the confusion.

comment:13 in reply to:  12 Changed 22 months ago by rebbecca

Replying to ln5:

Replying to ln5:

Setting svg.in-content.enabled = false makes Twitter web work as expected again in my Tor Browser 7.5a7, even on security level high.

That came out wrong. s/false/true/1, so what I meant to say was:

Setting svg.in-content.enabled = true makes Twitter web work as expected
                                 ^^^^

Sorry about the confusion.

No worries. thank you for the reply that fixed the problem.
also thanks to GeKo.

so finally setting svg.in-content.enabled to true on about:config solved the issue.

comment:14 Changed 22 months ago by rebbecca

Resolution: worksforme
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.