W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 11960] Consider making the global scope pollution by names/ids quirks-only

From: <bugzilla@jessica.w3.org>
Date: Tue, 29 Mar 2011 00:23:48 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q4Miq-0001YL-9T@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11960

--- Comment #12 from Jacob Rossi [MSFT] <jrossi@microsoft.com> 2011-03-29 00:23:44 UTC ---
We certainly wish to raise the bar for what gets added to the global namespace
in the future. However, we broke quite a number of top sites when we adjusted
how this behaved for just OBJECT/EMBED elements which ultimately resulted in us
having to alter our behavior (see
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12091). Given this experience,
we're not in favor of making this a quirk. 

Some of these sites do provide fallback using the document or getElementById,
etc. But I'm certain we saw some that didn't (and thus, I would assume were
broken in Gecko).

The impact of having names/ids in global scope is minimized by how they have
the lowest precedence when JavaScript searches for a given API.  

In case there was any confusion, IE9 follows the current spec text for name/id
resolution on the window:

•a, applet, area, embed, form, frame, frameset, iframe, img, or object elements
that have a name content attribute whose value is name, or
•HTML elements that have an id content attribute whose value is name.

http://dev.w3.org/html5/spec/Overview.html#dom-window-nameditem

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 29 March 2011 00:23:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 March 2011 00:24:00 GMT