3 ms·
http://code.google.com/p/chromium/issues/detail?id=18125 http://code.google.com/p/chromium/issues/detail?id=18125 "The upstream work is not sufficient for what
by jsz0 16y ago
http://code.google.com/p/chromium/issues/detail?id=18125 http://code.google.com/p/chromium/issues/detail?id=18125
"The upstream work is not sufficient for what we will need. It is only the beginning of the work. We would need to offload compositing to the GPU."
Sounds like Apple decided to enable the existing WebKit implementation while Google is working on their own implementation. (which could very well end up back into WebKit proper at some point) This is exactly how standards in the context of friendly competition are supposed to work. You can't really expect everyone working off WebKit code to coordinate when certain features or standards support are turned on in beta or public releases.
- DrSprout 16y agoThat's fine for development, but it's simply untrue to show features in development and claim that they represent usable support for standards.