- From: <bugzilla@jessica.w3.org>
- Date: Sun, 26 Sep 2010 11:57:21 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10355 --- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-09-26 11:57:21 --- Sample: data:text/html,<!doctype html> <marquee direction=up>Hello</marquee> <script> var el = document.createElement("marquee"); el.setAttribute("direction", "up"); alert(el.direction); </script> In Chrome dev, recentish Firefox mozilla-central, and Opera 10.60, the direction=up effect works, but Chrome and Firefox alert "undefined" (Opera alerts "up"). So it seems like at least some of the content attributes work without corresponding IDL attributes being defined. More comprehensive survey of IDL attribute support: data:text/html,<!doctype html> <script> var span = document.createElement("span"); var attrs = []; for (var attr in document.createElement("marquee")) { if ( !(attr in span) ) { attrs.push(attr); } } alert(attrs.join(" ")); </script> * IE8: bgColor vspace direction height behavior width loop scrollAmount trueSpeed scrollDelay onfinish onbounce onstart hspace * Recent Firefox mozilla-central build: align * Chrome dev: start stop * Safari 5: start stop * Opera 10.60: behavior direction height hspace loop scrollAmount scrollDelay vspace width start stop The intersection of any *two* of Trident, Gecko, and WebKit is apparently zero IDL attributes, so I expect they could all safely be removed from a web compat perspective. This makes <marquee> weirder (content attributes that work with no corresponding IDL attributes), but it's surely easier to reach compat by removing useless stuff than by trying to make <marquee> saner, even if it makes an obsolete part of the platform that much less logical. -- 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 Sunday, 26 September 2010 11:57:24 UTC