tl;dr - When applied to window.onerror information, the same-origin policy
makes it near-impossible to host script resources on a CDN, while
simultaneously using window.onerror to gather information about JS errors.
(fwiw, this issue also appears in
https://bugs.webkit.org/show_bug.cgi?id=70574)
Gecko's patch seems to have landed and there's a patch for webkit waiting
for review [1].
I believe the consensus in the bugs is for it to work just like it does
for img.
Any thoughts?
Cheers,
/pf
[1] https://bugs.webkit.org/show_bug.cgi?id=81438 (just for the
crossorigin attribute, the error sanitation part of robert's feature
request is still pending).
--
pablo flouret
motorola | webkit / browser team