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
– Updated:
–
public
Mentions:
@glennjones are these implementation issues or spec ones?
– Tobie Langel on twitter
@glennjones incidentally, that's why we need more tests. /cc @w3ctag
– 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?
– Ade Bateman on twitter
@adrianba agreed. Still, that makes it painful for devs. There must be a better way. @glennjones
– Tobie Langel 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
– Glenn Jones on twitter
@adrianba I don't know. Would not shipping a partial implementation help? @glennjones
– Tobie Langel 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).
– Ade Bateman on twitter
@adrianba sounds like the @urlstandard should have taken that in account then. @glennjones
– 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!
– 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.
– 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.
– Tobie Langel on twitter
@adrianba well, according to @glennjones, there is: lots of try..catch wrapping in lieu of feature detection.
– Tobie Langel on twitter
@glennjones that's a tough one indeed. What else could IE do not to cause that issue? /cc @adrianba
– Tobie Langel on twitter
@adrianba I'm not blaming IE, btw. We just don't have a good story for these issues. @glennjones
– Tobie Langel on twitter
@tobie the examples for URL and URLUtils polyfills are having to use try/catch to get around this. Similar issues with DOMParser
– Glenn Jones on twitter
@tobie @adrianba @w3ctag its an issue with API design, developer expectations and documentation. Wrote post: http://bit.ly/1RkmWqP
– Glenn Jones 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
– Glenn Jones on twitter
@glennjones BTW, I expect IE11 to be around for a long time, but not IE10.
– Ade Bateman on twitter
@tobie @glennjones I don't think there is though.
– Ade Bateman on twitter