You may see more divergence where the element with the id is in the
source code in the HTML. The following should alert "undefined" iff
`x` is not a property of the global VO, but if `x` is a property of
GlobalScopePolluter and the GlobalScopePolluter is in the prototype of
the global object, then I believe the expected result would be to
alert the value of `x`, that being that div.
<div id="x"> a</div>
Browsers may vary in such cases. However, if you are using unique IDs
that are unlikely to clash, you won't have such problems.
So my namespace is joined by a global variable for every DOM element
that has an id. Ugh. What to do?
That's GLobalScopePolluter, a feature that MSIE developed for IE4.
Other browsers copied it. I think it was 1-2 weeks ago on the ML where
I explained more about it.