On Sat, Nov 15, 2008 at 5:19 AM, Mike Shaver <[EMAIL PROTECTED]> wrote: > 2008/11/14 Maciej Stachowiak <[EMAIL PROTECTED]>: >> Specifically, we expose a "filter" property on CSSStyleDeclaration, in >> support of the SVG filter CSS property. However, many sites test for >> "filter" to detect support for MSIE's proprietary "filter" property, which >> sadly has the same name but completely incompatible syntax. Thus, we return >> this kind of magical undetectable string so if tests don't detect us as IE. >> It works basically the same ways as Mozilla's undetectable document.all, >> which we also support. > > Our undetectable document.all works by returning a different value > from the property access depending on whether it's a "detecting" use, > like |if (document.all)| -- we don't use a magic falsy object (which I > think is a violation of E262, but I'd have to dig into the ToBoolean > bits to be sure).
It is common knowledge that the "undetectable" document.all is detectable through normal scripting practices. "all" in document http://my.opera.com/hallvors/blog/2008/01/25/document-all-true#comment4543577 The same is true for the filter property:- "filter" in document.body.style webkit: true. Standardizing an MSIE property that works differently than in MSIE creates compatibility problems on the web. A better alternative would be to use a different property name. > > Mike _______________________________________________ Es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
