[Unrelated] forum website goes to mobile look after Feb 5 update

[smac770]

Hello. Forum site is https://www.audiworld.com/forums/ If you go to the site in FF (no addons), it comes up fine. In FF+NS, it was fine yesterday afternoon. Then yesterday evening, it started coming up looking funny, like it was for a small touchscreen instead of the proper look.

I inquired to the AW admins; they said nothing changed on their end. Then I saw NS had an update yesterday. Even if I do "disable restrictions for this tab", nothing changes.

I went to https://www.whatsmyua.info/ in FF and FF+NS, and the information is the same for both (after I marked the site trusted; before that, the ua-parser-js was blank for FF+NS).

Best I can tell, it's something within NS, and not something I can amend except to full disable NS. But not sure what the actual break is. Thanks.

[Guest]

Well damn it. NS update was Jan 5, not Feb 5. So not directly related to an NS update then. I'm still at a loss to understand then why it started displaying the page wrong last night (and still does it wrong) and why "disable all tab restrictions" doesn't change anything, but disabling NS does.

[barbaz]

What other extensions are you using?

[smac770]

I don't run anything else. Just NS. I've got a few others installed from various events in the past, but only NS is enabled in about:addons. And none of that changed in the past 24 hours.

[barbaz]

I don't seem to be able to reproduce this, I only get one interface on that site and it looks like a desktop site to me?

As a test, please create a new, clean profile from scratch. Install only NoScript latest development build, leaving all the defaults.
Does the problem still exist?
If not, try exporting the NoScript settings from your main profile (NoScript Options > Export) and importing them into the clean profile by NoScript Options > Import. Does the problem then occur in the clean profile?

[smac770]

I have another computer with FF. On this one, AW comes up correctly in both FF and FF+NS. NS is also 12.1.1, and it's the only addon as well.

The difference is this other computer is Win10 (vs Win 7) and is latest FF 135.0. The Win 7 machine is running ESR FF 115.19.

I notice the list of sites when clicking on the NS icon slightly differs between the machines, too. The not-working ESR 115 window shows "...ajax.googleapis.com" (trusted), while the working latest 135 window does not show that entry. The rest of the listed sites are the same.

When setting "disable all restrictions for this tab", should the page operate like NS wasn't even enabled? Or are there some basics that simply are always active if NS is enabled that I should keep in mind? I've noticed in the past some pages, even when trusted, some things like buttons just would never work and such. Some sites I simply have to do in FF plain just to be sure they are operating 100% as should (banking, etc). But I much prefer general browsing with NS there.

I'll try your test on the ESR system

[smac770]

clean profile without NS shows the site as expected.
clean profile with NS is showing the site as expected, with AW as default setting or trusted setting.

I notice ajax.googleapis.com was trusted setting in the site list for the AW page right out of the box? Does NS config that site as trusted by default? All the other sites were default setting, as expected.

So I tried to clear cache data, no change. I then deleted all the cookies for AW (there were 76 of them). That restored the expected operation.

So not sure what happened. I assume somehow a cookie got set incorrectly last night and it was messing up the page processing.

I think an error in my process was testing FF vs FF+NS using two different profiles. I don't like to have to bounce NS on and off, so I just use two different profiles for with and without NS. I didn't try my normal profile with NS disabled. I probably would have seen the errant behavior and realized it wasn't NS if I disabled NS within the same profile and tried again.

Thanks for your time.

[barbaz]

I think an error in my process was testing FF vs FF+NS using two different profiles. I don't like to have to bounce NS on and off, so I just use two different profiles for with and without NS. I didn't try my normal profile with NS disabled. I probably would have seen the errant behavior and realized it wasn't NS if I disabled NS within the same profile and tried again.

Thanks for reporting back and recognizing this.

Note to anyone reading this thread, trying a new profile without NoScript is *not* equivalent to disabling NoScript. Being specific about this is critically important for useful troubleshooting suggestions.

When setting "disable all restrictions for this tab", should the page operate like NS wasn't even enabled?

Not completely. "Disable restrictions for this tab" is supposed to be equivalent to setting all the permissions controlled by the Default/Trusted/Untrusted/Custom presets all set to allowed for everything that loads in that tab. It does not turn off other components of NoScript such as the XSS filter and the Cross-tab identity leak protection.

I notice ajax.googleapis.com was trusted setting in the site list for the AW page right out of the box? Does NS config that site as trusted by default? All the other sites were default setting, as expected.

NoScript does set some sites to Trusted by default. Most of the information in https://classic.noscript.net/faq#qa1_5 is still current

[smac770]

Appreciate all your support efforts, and the fabulous addon. Have a good one.