5 ms·
The problem is that the Chrome team shouldn't be selectively implementing parts of the html5 standard [1]. It shouldn't matter how many users desire the functio
by ovangle 13y ago
The problem is that the Chrome team shouldn't be selectively implementing parts of the html5 standard [1]. It shouldn't matter how many users desire the functionality after it's accepted by the w3c.
Of course, Chrome could implement whatever it likes if it drops any claim to be standards compliant, but until that happens...
[1] http://www.w3.org/Math/draft-spec/mathml.html http://www.w3.org/Math/draft-spec/mathml.html
- deleted 13y ago[deleted]
- ovangle 13y agoUmmm, no. It is part of the html5 spec, under embedded content. http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#mathml http://www.w3.org/html/wg/drafts/html/master/embedded-conten...
- anon1385 13y agoIs that a meaningful distinction? <img>, <video>, <audio> and <math> are all on this page: http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#mathml http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0....
- mddw 13y agoWhat ? Of course they should. It's all about choice. There are a shitload of standards and a limited amount of man-hour.