> 1. design a flawed API (it's fine! APIs are hard) > 2. ship it in the most-used browser, despite objections > 3. get cross-browser working group to fix the

> 1. design a flawed API (it's fine! APIs are hard) > 2. ship it in the most-used browser, despite objections > 3. get cross-browser working group to fix the API > 4. oops, too late, that would break the web Is this about DOMParser? (Which upon a parse error generates a DOM tree with an 'error document' instead of returning null or throwing an exception...)