URL use errors in IE/Edge #398

Activity

1. guybedford commented on Jun 12, 2015

   

   guybedford

   on Jun 12, 2015

   Member

   More actions

   Thanks! Is there an alternative you would suggest? Is there a better way to call it in Edge?
2. jdalton commented on Jun 12, 2015

   

   jdalton

   on Jun 12, 2015

   Author

   More actions

   The URL constructor is currently marked as "under consideration" on status.modern.ie. So it looks like IE/Edge's is from an earlier form of it. I think modifying the feature check from:

   var URL = typeof __global.URL == 'function' && __global.URL || URLPolyfill;

   to something like

   var URL = URLPolyfill;
   try { URL = (new __global.URL('http://')).protocol == 'http:' && __global.URL; } catch(e) {}

   should do it.
3. guybedford commented on Jun 13, 2015

   

   guybedford

   on Jun 13, 2015

   Member

   More actions

   Thanks, the build in this project actually always uses the polyfill directly - it's just SystemJS that loads it as a separate step. Mainly because there is a lot of pressure to show a low footprint loader.

   Fixed this up in SystemJS at systemjs/systemjs@47d9bf0.
4. guybedford

   closed this as completedon Jun 13, 2015
5. probins commented on Jun 13, 2015

   

   probins

   on Jun 13, 2015

   Contributor

   More actions

   strange: according to https://developer.mozilla.org/en-US/docs/Web/API/URL#Browser_compatibility the URL constructor is supported in IE from v10. Is that not correct?
6. jdalton commented on Jun 13, 2015

   

   jdalton

   on Jun 13, 2015

   Author

   More actions

   While the URL function exists, calling it as a constructor, a relatively newer addition, is not supported yet.
7. probins commented on Jun 13, 2015

   

   probins

   on Jun 13, 2015

   Contributor

   More actions

   ah yes, right, that's this page https://developer.mozilla.org/en-US/docs/Web/API/URL/URL