W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7851] Some (perhaps all) scripts with a for="" attribute should be ignored

From: <bugzilla@wiggum.w3.org>
Date: Fri, 09 Oct 2009 11:16:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MwDSn-0007wR-0T@wiggum.w3.org>

Michael A. Puls II <shadow2531@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |shadow2531@gmail.com

--- Comment #1 from Michael A. Puls II <shadow2531@gmail.com>  2009-10-09 11:16:44 ---
Not sure if it's still true, but not long after the FF WMP plug-in
came out, I noticed that Firefox supported <script for="" event=""> just like
IE does with the WMP activex plug-in.

In other words, Firefox was/is passing

That caused/causes a problem because other browsers besides IE don't support
that. For other browsers, you need to define a global function: 
function OnDSPlayStateChangeEvt(newState) {
instead. (The plug-in supports both the 6.4 api and the 7+ api).

There was even a site that assumed all browsers did like FF and it broke in
Opera. Unfortunately, I can't find the site atm.

With that said, we really shouldn't touch that IEism with a 10ft pole. However,
'we just refuse to execute any script where the script element has a
for="" attribute.' makes the best sense *if* we want to handle that. Scripts
like that should still be invalid of course.

(IE also supports attachEvent on that WMP plug-in to handle things, which also
doesn't work in other browsers.)

Whatever is done, for="" should be strongly discouaraged.

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 Friday, 9 October 2009 11:16:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:41 UTC