HappyInTheWest wrote:Hello - thanks for being here to answer questions. I have nowhere near the technical vocabulary and expertise you all do, so please speak slowly and use small words!
I'm on a 2014 Mac Air updated to High Sierra and FF Quantum.
This morning Twitter on Firefox started redirecting to the mobile site. In about:config I restored all the "useragent" lines to default, and restarted. No change.
Firefox in safe mode didn't have the problem.
So I disabled my add-ons one at a time, and it turned out NoScript is the villain. I reproduced the result twice.
What's my next step? I want to re-enable NS as soon as possible.
That was standard behaviour of NS before Quantum, too.
If you don't allow the specific scripts, Twitter thinks that blocking the scripts means that you are on a mobile platform that doesn't have scripts, and redirects you.
So reactivate NS, check if you are running the current version (10.1.3)
then check if your settings for "default, untrusted and trusted" are correct
And then make a rule for "
https://twitter.com/" (that's enough to stop the redirect for me)
you still need to allow other scripts (like twtimage for content).
[quote="HappyInTheWest"]Hello - thanks for being here to answer questions. I have nowhere near the technical vocabulary and expertise you all do, so please speak slowly and use small words!
I'm on a 2014 Mac Air updated to High Sierra and FF Quantum.
This morning Twitter on Firefox started redirecting to the mobile site. In about:config I restored all the "useragent" lines to default, and restarted. No change.
Firefox in safe mode didn't have the problem.
So I disabled my add-ons one at a time, and it turned out NoScript is the villain. I reproduced the result twice.
What's my next step? I want to re-enable NS as soon as possible.[/quote]
That was standard behaviour of NS before Quantum, too.
If you don't allow the specific scripts, Twitter thinks that blocking the scripts means that you are on a mobile platform that doesn't have scripts, and redirects you.
So reactivate NS, check if you are running the current version (10.1.3)
then check if your settings for "default, untrusted and trusted" are correct
And then make a rule for "https://twitter.com/" (that's enough to stop the redirect for me)
you still need to allow other scripts (like twtimage for content).