3 ms·
Google doesn't need to officially fork WebKit, it can keep these features in Chromium and not push them into WebKit - like many other features, including the on
by azakai 14y ago
Google doesn't need to officially fork WebKit, it can keep these features in Chromium and not push them into WebKit - like many other features, including the one you mentioned (Dart support that Apple rejected). But Chrome is still a major implementation, it doesn't have to get into WebKit or not (for standardization purposes that we are discussing here).
- kibwen 14y agoThanks, I wasn't sure what was considered an "implementation" according to the W3C. In other news, azakai, you work for Mozilla, correct? Have they issued an official statement regarding this?
- azakai 14y agoNot to my knowledge. But it is very possible I just didn't hear a statement if there was one ;)
- bzbarsky 14y agoChrome certainly counts as an implementation. You just can't count Chrome and Safari as two separate implementations if the actual code is in shared WebKit (but you _can_ count them if the implementation is unshared code, for what it's worth). As for Mozilla, no official statement yet, though there have been some public comments from Robert O'Callahan on the EME spec.