4 ms·
To me this just prove that wether a spec or standard is in place. it does not really matter. In this case we have the weight of Google that says "oh it's in th
by zwetan 10y ago
To me this just prove that wether a spec or standard is in place. it does not really matter.
In this case we have the weight of Google that says "oh it's in the spec so we can do it".
In other case we have a standard like E4X, that everyone happily not implemented (Chrome) or removed (Firefox).
They could as well say "If we don't like it we will not do it, if we like it we will do it", that would be exactly the same.
- TheRealPomax 10y agoalmost. It would be exactly the same if it was "If we don't like it we will not do it, if we like it we will do it, and in both cases we set up a w3 working group for writing the formal declaration that this is what we now agree on". Welcome to HTML5: a document that comes out of the work of tens of thousands of people across decades of historically-encumbered practices. It's done remarkably well, and if you actually read the spec, is way more sensible than you would think that development track would give us.