Flash needs to be Forbidden for this to occur.
If Flash is allowed, the player (automatically) loads only once.
And possibly the cause? In the case of electronic-arts.de, it is refreshing the Flash, I'm suspecting loading a "new" movie each time. When Flash is Allowed, it does so in a singular player. When Flash is Forbidden, each time it "refreshes", NoScript is seeing a new Flash "item", & generates another placeholder for it.
This looks not to occur in Gecko 1.9.+
Both an0nymoose & Guest123 are running FF2 (Gecko 1.8.1).
Is it maybe not necessarily repeatable, or are there other factors involved too?
I put NoScript 1.9.1 in SeaMonkey looking for a regression range, but now cannot make it occur even with going back to 1.9.1.5?
(SeaMonkey can be a bit peculiar. Like I have 1.9.1.6 in one instance/Profile, & I can have 1.8.0 in another instance/Profile, which I suppose can cause oddities.)
Ha! And I saw this too in FF2. Trying to think ... Whatever version of NoScript that had been installed in FF2, I updated to 1.9.1.6 (thinking the problem lie there). Restarted & I saw the problem. Again looking for regression, I installed 1.9.1, Restarted, but no problem. Understandable
. But now having put 1.9.1.5 in (happened to be closer to hand then 1.9.1.6), I am no longer seeing it?
install.log, FF2
Code: Select all
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/noscript-1.8.3.3.xpi -- 2008-10-22 11:04:31
-------------------------------------------------------------------------------
Install completed successfully -- 2008-10-22 11:04:31
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/flashgot-1.1.3.1-dev.xpi -- 2008-11-03 15:45:15
-------------------------------------------------------------------------------
Install completed successfully -- 2008-11-03 15:45:15
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/noscript-1.9.1.6.xpi -- 2009-04-02 13:53:03
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 13:53:03
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.xpi -- 2009-04-02 14:25:56
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 14:25:56
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.5-dev.xpi -- 2009-04-02 14:26:32
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 14:26:33
So initially I had 1.8.3.3 installed. (Don't believe I tested initially with that?) Installed 1.9.1.6. Saw the problem. Reverted back to 1.9.1. Problem not visible. Put in 1.9.1.5. Problem still not visible?
More aha. Putting 1.9.1.6 back in & the problem returns. So is 1.9.1.6 making earlier versions susceptible too? No probably not. Putting 1.9.1.5 back in (& this is in FF now) & I'm not seeing the problem. Seeing it (originally) in SeaMonkey (& with 1.9.1.5) may have had to do with having different versions installed (1.9.1.6 in my main Profile & something else in my "cleaner" Profile)?
install.log, SeaMonkey 1.1.16
Code: Select all
file:///L:/LIB/NETT/Mozilla/noscript-1.9.1.5-dev.xpi -- 2009-03-27 16:50:10
file:///C:/WLIB/LeechFTP/LEECHTMP/noscript-1.9.1.6.xpi -- 2009-04-02 09:26:09
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.xpi -- 2009-04-02 14:16:47
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.1-dev.xpi -- 2009-04-02 14:17:45
... file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.5-dev.xpi -- 2009-04-02 14:19:52
So (in my main Profile & presumably my "clean" Profile too), I had 1.9.1.5 installed. This morning (in my main Profile only) I installed 1.9.1.6. Opening my "clean" Profile I saw the issue from the onset - but note it only had 1.9.1.5 installed. (All the remainder of the SeaMonkey testing was with my "clean" Profile.) That points to the issue being with 1.9.1.6 specifically. So when I reverted back to 1.9.1 it replaced the NoScript parts that get installed globally (that were previously at version 1.9.1.6) with 1.9.1 where the problem does not occur. And then when I went forward (but only up to 1.9.1.5, where the problem did not exist), that caused me not to see the issue.
If I now put 1.9.1.6 into my clean Profile, it should return there. Or if I reinstalled it into my current Profile, I should see the issue in my clean Profile even though it is (currently) at 1.9.1.5. (Eh,...? Maybe, maybe not. I'm to the point where I've done too many ins & outs that I don't know where I am anymore
.)
And with that, does the problem exist with noscriptService.js ? (Again, maybe?)
Neat.
Flash needs to be Forbidden for this to occur.
If Flash is allowed, the player (automatically) loads only once.
And possibly the cause? In the case of electronic-arts.de, it is refreshing the Flash, I'm suspecting loading a "new" movie each time. When Flash is Allowed, it does so in a singular player. When Flash is Forbidden, each time it "refreshes", NoScript is seeing a new Flash "item", & generates another placeholder for it.
This looks not to occur in Gecko 1.9.+
Both an0nymoose & Guest123 are running FF2 (Gecko 1.8.1).
Is it maybe not necessarily repeatable, or are there other factors involved too?
I put NoScript 1.9.1 in SeaMonkey looking for a regression range, but now cannot make it occur even with going back to 1.9.1.5?
(SeaMonkey can be a bit peculiar. Like I have 1.9.1.6 in one instance/Profile, & I can have 1.8.0 in another instance/Profile, which I suppose can cause oddities.)
Ha! And I saw this too in FF2. Trying to think ... Whatever version of NoScript that had been installed in FF2, I updated to 1.9.1.6 (thinking the problem lie there). Restarted & I saw the problem. Again looking for regression, I installed 1.9.1, Restarted, but no problem. Understandable ;-). But now having put 1.9.1.5 in (happened to be closer to hand then 1.9.1.6), I am no longer seeing it?
[b]install.log, FF2[/b]
[code]
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/noscript-1.8.3.3.xpi -- 2008-10-22 11:04:31
-------------------------------------------------------------------------------
Install completed successfully -- 2008-10-22 11:04:31
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/flashgot-1.1.3.1-dev.xpi -- 2008-11-03 15:45:15
-------------------------------------------------------------------------------
Install completed successfully -- 2008-11-03 15:45:15
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/noscript-1.9.1.6.xpi -- 2009-04-02 13:53:03
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 13:53:03
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.xpi -- 2009-04-02 14:25:56
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 14:25:56
-------------------------------------------------------------------------------
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.5-dev.xpi -- 2009-04-02 14:26:32
-------------------------------------------------------------------------------
Install completed successfully -- 2009-04-02 14:26:33
[/code]
So initially I had 1.8.3.3 installed. (Don't believe I tested initially with that?) Installed 1.9.1.6. Saw the problem. Reverted back to 1.9.1. Problem not visible. Put in 1.9.1.5. Problem still not visible?
More aha. Putting 1.9.1.6 back in & the problem returns. So is 1.9.1.6 making earlier versions susceptible too? No probably not. Putting 1.9.1.5 back in (& this is in FF now) & I'm not seeing the problem. Seeing it (originally) in SeaMonkey (& with 1.9.1.5) may have had to do with having different versions installed (1.9.1.6 in my main Profile & something else in my "cleaner" Profile)?
[b]install.log, SeaMonkey 1.1.16[/b]
[code]
file:///L:/LIB/NETT/Mozilla/noscript-1.9.1.5-dev.xpi -- 2009-03-27 16:50:10
file:///C:/WLIB/LeechFTP/LEECHTMP/noscript-1.9.1.6.xpi -- 2009-04-02 09:26:09
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.xpi -- 2009-04-02 14:16:47
file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.1-dev.xpi -- 2009-04-02 14:17:45
... file:///L:/LIB/NETT/Mozilla/OLD/noscript-1.9.1.5-dev.xpi -- 2009-04-02 14:19:52
[/code]
So (in my main Profile & presumably my "clean" Profile too), I had 1.9.1.5 installed. This morning (in my main Profile only) I installed 1.9.1.6. Opening my "clean" Profile I saw the issue from the onset - but note it only had 1.9.1.5 installed. (All the remainder of the SeaMonkey testing was with my "clean" Profile.) That points to the issue being with 1.9.1.6 specifically. So when I reverted back to 1.9.1 it replaced the NoScript parts that get installed globally (that were previously at version 1.9.1.6) with 1.9.1 where the problem does not occur. And then when I went forward (but only up to 1.9.1.5, where the problem did not exist), that caused me not to see the issue.
If I now put 1.9.1.6 into my clean Profile, it should return there. Or if I reinstalled it into my current Profile, I should see the issue in my clean Profile even though it is (currently) at 1.9.1.5. (Eh,...? Maybe, maybe not. I'm to the point where I've done too many ins & outs that I don't know where I am anymore ;-).)
And with that, does the problem exist with noscriptService.js ? (Again, maybe?)
Neat.