Page 1 of 1
NoScript on strava.com when blocking twitter.com
Posted: Wed Oct 09, 2013 9:20 pm
by Guest
I regularly upload to Strava.com using FireFox and NoScript.
However recently I have had to enable access to twitter.com to be able to see all the maps, charts, and to activate buttons on Strava.
Strava claims the problem is with NoScript and not with any changes Strava have made.
Is there any way to narrow the problem down further?
Re: NoScript on strava.com when blocking twitter.com
Posted: Thu Oct 10, 2013 3:53 am
by Thrawn
Anything relevant in the Browser Console? Tools - Developer - Browser Console or Ctrl+Shift+J.
Re: NoScript on strava.com when blocking twitter.com
Posted: Thu Oct 10, 2013 1:31 pm
by Guest
I am not sure what to look for, but I find this when I try and load the page with twitter.com denied:
Code: Select all
TypeError: window.twttr is not a function
TypeError: Strava.Util.DropDownMenu is not a constructor
TypeError: Strava.Util.DismissController is not a constructor
TypeError: Strava.Ui.LightboxView is not a constructor
Use of getPreventDefault() is deprecated. Use defaultPrevented instead.
TypeError: Strava.Util.Url is undefined
When I allow twitter.com then I do see this:
Code: Select all
Warning: attempting to write 6161 bytes to preference sites. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file.
GET http://platform.twitter.com/widgets.js [HTTP/1.1 200 OK 80ms]
Use of getPreventDefault() is deprecated. Use defaultPrevented instead. @ http://d26ifou2tyrp3u.cloudfront.net/assets/strava-jquery-727e9bc1bc9ad1f0497b59fe553d2dd1.js:17
Re: NoScript on strava.com when blocking twitter.com
Posted: Thu Oct 10, 2013 11:29 pm
by Guest
Strava Support has decided that FireFox v24 is the problem.
Strava Support Team Oct 10 04:04 pm (PDT) wrote:
Hello,
Thank you for your patience while I've tried to investigate this issue. It seems that this new version of FireFox is confusing our system and not allowing the data to be displayed when you log-in. Instead, it seems that Twitter is able to recognize this better than we are at the moment. Hopefully, this is something that we will be able to fix in the near future. I do apologize for the inconvenience, please let me know if you have any further questions.
Regards,
Katherine
Strava Support Team