2 ms·

Daniel Glazman (W3C CSS Working Group co-chair) gives a few more examples from a CSS point of view: http://www.glazman.org/weblog/dotclear/index.php?post/2010/0

Daniel Glazman (W3C CSS Working Group co-chair) gives a few more examples from a CSS point of view: http://www.glazman.org/weblog/dotclear/index.php?post/2010/04/30/Innovation-browsers-CSS-and-chutzpah http://www.glazman.org/weblog/dotclear/index.php?post/2010/0... Yet another example is "viewport" meta tag, which Mobile Safari introduced, Android later adopted, and which we (Mozilla) are now adding to mobile Firefox. There's no spec for this anywhere; it will probably be implemented in half a dozen mobile browser engines before even a draft spec is written. Now, it's clear from all these examples that Sachin and Joe's description of the situation are factually wrong. But that doesn't mean they don't have a point. The problems they feel with web development may indeed exist, but with some other cause than the one they imagined.

wycats 17y ago
@mbrubeck I totally agree that there is a real problem, but from all the responses, I think it's actually the opposite of what they're saying. People say "it's all well and good that Mobile Webkit has hardware accelerated transforms, but I can't use it in IE". In other words, people are (correctly) seeing that despite the rapid innovation, the lowest-common-denominator of browsers in use is changing rather slowly. And that's frustrating. Apple's work on Mobile Safari clearly puts the lie to Joe's argument about browser innovation on the iPhone (which is where his experience lies). I see plenty of evidence that Apple and others are improving the underlying browser engine, and that Apple is adding mobile features to their iPhone browser, and no evidence to the contrary.