InformAction Forums

Hello,

I hope I have posted in the right place to report a bug?

I have a topic with the basics at DSLR posted here:
http://www.dslreports.com/forum/r305331 ... site-issue

I have both the browser and NoScript updated to the latest versions with site no luck.

Waterfox 44.0.3
NoScript 2.9.0.9

But as mentioned in the topic, it was working fine in Waterfox 43.0.3 before the change of the compiler.
However in a limited user account it breaks, yet an admin account it is fine.

Maybe someone can duplicate it and if it isn't NoScript then report it to the browser's developer as nothing seems to change the behavior.

Thanks

Waterfox is not a supported browser. Please test NoScript latest development build in the corresponding Firefox or SeaMonkey version and let us know if the problem still occurs, thanks.

Hello barbaz

Thank you for the reply - and for the information Firefox does not work for this subject.
However Waterfox is still installed.
Plug-ins are:
Ghostery
NoScript
uBlock Origin

Edit: To add - Firefox is the default browser for the check.

All updated but at the time of testing with Waterfox no other plug-ins were installed and it was fresh installs etc so I'm expecting nothing to change now Firefox is doing it too.
Short of the full clean install and all that (Firefox has only been installed for this test); is there any logs I can product that might assist this request for your review?

Thanks

Please disable Ghostery for testing; it's notorious for causing all sorts of weird issues and incompatibilities.
(I don't think uBlock Origin would cause this; it's definitely not a default setting and I've confirmed that the frame loads for me without touching my much restrictive uBlock Origin settings.)


Hang on, when you say the frame not load, do you really mean this? [x]
EDIT And I can confirm that it works in a new tab.

EDIT2 When it fails, do you see this console message? I don't know what it means though

Not clear on what you're saying, but FF 45.0.1 x64 & NoScript 2.9.10 works as expected with www.meteorology.com.au/radar, so disable all other extensions & test.

And once you know that works, then figure out which extension is actually blocking you (in FF). (Then see if the same holds true in Cyberfox.)

barbaz wrote:Please disable Ghostery for testing; it's notorious for causing all sorts of weird issues and incompatibilities.
(I don't think uBlock Origin would cause this; it's definitely not a default setting and I've confirmed that the frame loads for me without touching my much restrictive uBlock Origin settings.)


Hang on, when you say the frame not load, do you really mean this? http://postimg.org/image/h9cqod87z/
EDIT And I can confirm that it works in a new tab.

EDIT2 When it fails, do you see this console message?

Code: Select all

SecurityError: The operation is insecure.1 animator-2.01.min.js:4:0

I don't know what it means though

Yes, that is exactly the issue I am asking for help on barbaz.
Do you know a way to fix it as I'm at my wits end trying to figure out what is causing it.

therube wrote:Not clear on what you're saying, but FF 45.0.1 x64 & NoScript 2.9.10 works as expected

Yes the majority of people don't see a problem and only 3 has reported the issue including myself - at least barbaz has, to help understand, even if unsure of what is doing it.

It occurs once NoScript is installed and it has only become a problem since the Intel compiler started to be used for the browser (in the last few months).
It was never a problem before that so it may yet be a browser issue not a NoScript issue.

norwegian wrote:Yes, that is exactly the issue I am asking for help on barbaz.
Do you know a way to fix it as I'm at my wits end trying to figure out what is causing it.

Thanks for clarifying.
Not sure yet why that's happening, I will look into it in more detail probably tomorrow.

Thanks, and when you can, as you say the frame will load in a new tab for viewing which covers my needs initially
I'll agree it is a strange one, the fact it's blocked but then still loads with no settings change.

Not related to NoScript at all, at least here - the radar works for me if I have 3rd-party cookies enabled, and not otherwise. (Weird that I don't even have to unblock 3rd-party cookies in µMatrix, just the browser...)

Moving to NoScript Support.

(... vague memory of some sort of recent Intel video, HD4000 & older driver or some such, related bug ... I have on chip HD4000 & am not affected.)

barbaz wrote:Not related to NoScript at all, at least here - the radar works for me if I have 3rd-party cookies enabled, and not otherwise. (Weird that I don't even have to unblock 3rd-party cookies in µMatrix, just the browser...)

Moving to NoScript Support.

That is strange - I've had block third party cookies forever and never allow them full stop.
Something at the web site must have changed around the same time as the compiler changes and it was coincidence.

Thank you for the time to look into this one, but makes me feel a little foolish for not doing that sort of check myself.

therube wrote:(... vague memory of some sort of recent Intel video, HD4000 & older driver or some such, related bug ... I have on chip HD4000 & am not affected.)

I have a HD4600 for graphics and have had the same drivers installed for 6 months or so and it's only started recently.

For now I've just allowed these sites in cookie handling.

norwegian wrote:That is strange - I've had block third party cookies forever and never allow them full stop.
Something at the web site must have changed around the same time as the compiler changes and it was coincidence.

Thank you for the time to look into this one, but makes me feel a little foolish for not doing that sort of check myself.

You're welcome.
Correct me if I'm wrong, but didn't you say (in the dslreports thread) that disabling NoScript makes it work for you? Which would indicate that the cause of the issue on your end maybe something else than the cause on my end... or did allowing those 3rd-party cookies get it working for you too?

Correct, that was the behavior at the time and in an admin acct it was fine, and in a limited user it wasn't. Note though the admin acct stopped functioning too.
That is why I came here to discuss the issue.
I have tested without plugins running and it is cookie handling that changes it now.
Which leads to browser changes in builds that might have been the root of the issue.
The first time I had this issue was with 43.0.4 and since have updated to 44.0.3 in Waterfox - which is showing the same behavior as Firefox for you and cookies.