Benjamin Hawkes-Lewis wrote: > Indeed, but note that's true for JS too. For example, you can detect > getElementById but you can't be sure it won't get elements by NAME too > (as the JScript implementation does). But JS feature detection is still > generally preferable to browser detection. But perhaps one would need > both to work around known broken implementations. Perhaps one could add engine detection to the @feature syntax to encourage authors to feature detect before they engine-detect, rather than having a separate @ua statement, like so: @feature (display: inline-block;) with engine(Gecko, <= 1.9) { /* Gecko's known broken implementation of inline block. */ } -- Benjamin Hawkes-LewisReceived on Friday, 23 November 2007 08:52:46 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 November 2007 08:52:47 GMT