4 ms·
So... one should never use features that aren't already in the standard? Sure, that's one approach. But what if you want one of those features?
by eli 15y ago
So... one should never use features that aren't already in the standard?
Sure, that's one approach. But what if you want one of those features?
- EGreg 15y agoThe browser makers should always be compatible with the standard, the new features shouldn't break the expectations of web page creators which they get after reading the standard. http://www.quirksmode.org/ http://www.quirksmode.org/
- angersock 15y agoSpoken like someone who probably has never had to deal with vendor extensions to OpenGL... :( Try to fix your standards body and get them to move faster!
- gcp 15y agoThe problem of a standards body is that it requires everyone involved to have an interest in having a common standard. When this is the case, they work fine. When this is not the case, you're SOL. Do you think Apple and Google have an interest in making mobile sites work on Windows Phone, or phones with Opera Mini?
- tomjen3 15y agoHonestly I put in css which _does the very same thing_ for each of the major browsers and then once more with no prefix. So standardize it already. It is a defactor standard, so why haven't the standard organizations made it yet?