4 ms·

It looks like it only exports webkit-compatitble CSS. If this is the case, this would be really disappointing.

• whalesalad 14y ago
  Not nearly as disappointing as the fact that Webkit has not become a standard in all browsers. We should all be working on a single rendering engine. Webkit has won, and should be the standard. People/organizations can continue to experiment on components of that. V8 vs Nitro etc... We'll just have beta/dev forks of Webkit that can eventually be merged back into the core. Browser fragmentation is fine. It's the rendering engines that are killing us.
  • cleverjake 14y ago
    the html5 spec specifies exact parser behavior, and ensures the same rendering across all compliant browsers. If we did standardize rendering engines (which could /never/ happen, for an incredible number of sociopolitical reasons), what fragmentation would exist? Competition creates innovation.
  • darkstalker 14y ago
    CSS prefixes are dumb, why not just drop them?
    • mas1n 14y ago
      http://www.alistapart.com/articles/prefix-or-posthack http://www.alistapart.com/articles/prefix-or-posthack
• tomaskafka 14y ago
  Hi, I'm dev from CSS Hat team - we will export regular CSS3, vendor extensions (webkit,moz,o) are optional. Thanks for interest! :)