Using Firefox 4.0b4 and NoScript 2.0.2.4rc1, I notice that the "Evalute" function in the Error Console seems to have stopped working. If I disable NoScript then it works again.
Normally, I can open Tools/Error Console, type in a Javascript expression in "Code" and select "Evaluate" to have the result of the expression on the console. But with NoScript installed I get
OK, so 123 is working.
(And so it was just the particular code that I posted that was failing.)
> or on a clean profile
Is this a clean profile with NoScript installed (at which point no longer clean .)
Running like that, NoScript enabled, 123 evaluates as expected for me (to 123).
Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100902 SeaMonkey/2.1b1pre
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.12) Gecko/20100825 SeaMonkey/2.0.7
It seems a change in how frame origins are computed in recent Minefield builds for content policy purposes.
In this case, when the console evaluated a script in its evaluation frame it used to be "seen" by content policies as a request originated by chrome://browser/console.xul, while now it looks like it is originated by about:blank (which seems a Firefox bug to me, but I'm still investigating).
The obvious work-around is allowing about:blank.