Temporary allow problem

[havelock]

Hi all,

I've discovered recently a problem : when I temporary allow JS execution on some pages, the code isn't executed, even after refreshing the page or opening multiple instances of it. However, if I close all the instances of the site and then reopen the link, it behaves nicely.

It appeared on https://play.rust-lang.org/ .

There is also another problem which may be linked to that one (but I don't know if it's more noscript or firefox-related) : when I open a specific page, if the JS on it isn't allowed, firefox crashes. If it's allowed, it works well.

I've only found that behaviour here : http://comic.naver.com/webtoon/detail.n ... 385&no=267 (others no= seem to do the same, but not all, afaik)

[barbaz]

I've discovered recently a problem : when I temporary allow JS execution on some pages, the code isn't executed, even after refreshing the page or opening multiple instances of it. However, if I close all the instances of the site and then reopen the link, it behaves nicely.

Does the same happen on a new, clean profile with only NoScript installed?

There is also another problem which may be linked to that one (but I don't know if it's more noscript or firefox-related) : when I open a specific page, if the JS on it isn't allowed, firefox crashes. If it's allowed, it works well.

I've only found that behaviour here :

The board broke your link, please re-post it in url tags, like this

Code: Select all

[url]link here[/url]

[therube]

> I temporary allow JS execution on some pages, the code isn't executed
> https://play.rust-lang.org/

What domains have you allowed there?

[havelock]

Yes, it also occured with an empty NS-only profile.

The first URL is http://comic.naver.com/webtoon/detail.n ... 385&no=267.

for the other URL, all scripts sites on the page were enabled.

[barbaz]

Does the problem with the first link (rust-lang) occur also without NoScript, but following these steps:
1) new profile as above, NO noscript install
2) about:config > set javascript.enabled to false
3) visit the site
4) in a new tab (leave the site open), about:config > set javascript.enabled to true
5) reload the site

If the problem does *not* occur with those steps, can you please reproduce the problem again (using NoScript) and post here any related messages you see in the Browser Console (Ctrl-Shift-J) and/or Web Console (Ctrl-Shift-K)?
(if you don't know what's related, turn off CSS warnings and post everything else you see)


Can you try also the second link in a new profile without NoScript but with about:config > javascript.enabled set to false , does it still crash?