No Globals not working in Opera

[paul999]

When using qunit with opera the noglobals option is generating failures:

Introduced global variable(s): test-output6, test-output7, test-output8, test-output9Source: ok( false, "Introduced global variable(s): " + newGlobals.join(", ") );

Opera version 11.61
Build 1250
Linux x64

[nimbupani]

Could you clarify exactly what is expected, and what is not working? Perhaps a pastie with the code you are working on would be useful. cc @miketaylr

[paul999]

Hi,

Expected is that there is no warning displayed about new global vars, in firefox and chrome this happens, in Opera it displays the error that there are new global vars.

You can see it happen here: http://js-linux.nl/Javascript-Linux/test.html?noglobals=true In some cases it happens in the first test, in some cases in the second test (It changes on a refresh), the mentioned globals are not from my code at all.
The code in that specif test is here: https://github.com/paul999/Javascript-Linux/blob/master/tests/general.js

[jzaefferer]

@nimbupani those globals are element IDs are generated by QUnit: https://github.com/jquery/qunit/blob/854308117e9e7dab00b67965ff37437739082b13/qunit/qunit.js#L45

The noglobals feature iterates over all window properties before and after running a test, marking any change as an error. It looks like in Opera, under some conditions, those DOM ids are exposed as window properties.

[miketaylr]

All browsers expose ids and name properties as globals, with the exception of Firefox which only does this in Quirks Mode. This is actually specced by HTML5, as terrible as it is. :/ (see https://www.w3.org/Bugs/Public/show_bug.cgi?id=11960)

Given that this warning doesn't happen in Chrome, could it be possible that it's something else?

[jzaefferer]

Gave up and implemented a workaround to ignore those keys when checking for pollution.