In reply to this conservation: Find it a little sad some of the browser APIs are introduced in such an incomplete state the only way to use them is in try/catch blocks 9 years ago – Glenn Jones on twitter @glennjones are these implementation issues or spec ones? 9 years ago – Tobie Langel on twitter @tobie just looking at URL and URLUtils the constructor of URL takes 2 arguments to resolve absolute URL, but the early IE version blows up 9 years ago ‐ Also on: Twitter | Favourite Retweet Reply Likes mozheykinanadya favorited this Mentions: @glennjones that's a tough one indeed. What else could IE do not to cause that issue? /cc @adrianba 9 years ago – Tobie Langel on twitter @adrianba agreed. Still, that makes it painful for devs. There must be a better way. @glennjones 9 years ago – Tobie Langel on twitter @tobie @glennjones I don't think there is though. 9 years ago – Ade Bateman on twitter @adrianba I don't know. Would not shipping a partial implementation help? @glennjones 9 years ago – Tobie Langel on twitter @tobie @glennjones IE10+ only supported the static methods on URL so there is no constructor. At the time what else could it do but throw? 9 years ago – Ade Bateman on twitter @adrianba sounds like the @urlstandard should have taken that in account then. @glennjones 9 years ago – Tobie Langel on twitter @tobie @adrianba I don't known the history, but it does look like the URL object should not have been extended in this way, not a IE issue! 9 years ago – Glenn Jones on twitter @glennjones @tobie It's complicated because I think things were proceeding in parallel. I actually don't think there is a problem here. 9 years ago – Ade Bateman on twitter @adrianba well, according to @glennjones, there is: lots of try..catch wrapping in lieu of feature detection. 9 years ago – Tobie Langel on twitter @adrianba I'm not blaming IE, btw. We just don't have a good story for these issues. @glennjones 9 years ago – Tobie Langel on twitter @glennjones incidentally, that's why we need more tests. /cc @w3ctag 9 years ago – Tobie Langel on twitter @tobie @adrianba @w3ctag its an issue with API design, developer expectations and documentation. Wrote post: http://bit.ly/1RkmWqP 9 years ago – Glenn Jones on twitter @tobie @w3ctag its a hard problem, but when you start to see cross browser code examples like https://developer.mozilla.org/en-US/docs/Web/API/DOMParser… I do start to worry 9 years ago – Glenn Jones on twitter @glennjones BTW, I expect IE11 to be around for a long time, but not IE10. 9 years ago – Ade Bateman on twitter @glennjones how to ship partial implementations that don't blow-up in devs' faces is something @w3ctag should help implementors with, imho. 9 years ago – Tobie Langel on twitter @glennjones Not wonderful, but you might be able to test window.URL.prototype.constructor.length or some such. @tobie @adrianba @w3ctag 9 years ago – Robin Berjon on twitter @tobie @glennjones We shipped a complete implementation of what was in the File API spec at the time (which only defined static members). 9 years ago – Ade Bateman on twitter