The_Decryptor, on 13 February 2013 - 09:56, said:
This "bug" has been in WebKit for years now, and they have no plans to fix it.
If WebKit becomes the "reference implementation" does that mean it should be part of the CSS spec?
When big guys join up (like Opera now) and hopefully Mozilla and Microsoft everyone would be contributing to the Webkit/Chromium code (whichever it is).
This would do several things;
1. Rapidly bring innovation and ubiquity among browsers.. new features would be matter of months to simply add and they would be immediately available on all other browsers.
2. Instead of writing 15 lines of CSS code and use polyfills and other garbage to work across browsers standards based stuff would just work the same on all browsers (including CSS)
3. Tools for animations, development would get into a second renaissance since Flash. Adobe and others could build awesome tools without worrying and generating kilobytes of code just to make simplest thing work on all browsers which in return makes it very hard to make good tools.
Right now, it's a mess and it's really killing the web as long as we have "Works exclusively with IE10" or "Works with Chrome" or whatever.. you wouldn't see that problem if they all agreed on one standards based, open source, browser engine.
I have no plan on waiting for next HTML improvements for another decade because of their own greed and desire for power. It's time they wake up and follow Opera.