14177 2011-09-16 07:06:24 +0000 onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) 2011-11-10 23:32:08 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#runtime-script-errors P3 normal --- 1 contributor ian ian mike Ms2ger public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 56884 0 contributor 2011-09-16 07:06:24 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html Multipage: http://www.whatwg.org/C#runtime-script-errors Complete: http://www.whatwg.org/c#runtime-script-errors Comment: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) Posted from: 85.227.155.223 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.51 56904 1 Ms2ger 2011-09-16 14:51:07 +0000 *** This bug has been marked as a duplicate of bug 14176 *** 56908 2 zcorpan 2011-09-16 17:02:40 +0000 It's not a dup (affects different part of the spec) 58475 3 ian 2011-10-19 23:20:12 +0000 Could you elaborate? 58580 4 zcorpan 2011-10-20 21:48:01 +0000 So for <script src> scripts, if the script's URL's origin (after redirects) is not the same as the script's origin, then in http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#runtime-script-errors the "report the error" should use the arguments ("Script error.", "", 0). 59029 5 ian 2011-10-26 23:57:30 +0000 I don't understand how this is not a dupe of bug 14176. Can you show a pair of examples that demonstrate how fixing bug 14176 would not fix this bug? 59051 6 zcorpan 2011-10-27 08:23:38 +0000 This bug is about http://www.whatwg.org/C#runtime-script-errors-in-documents i.e. uncaught exceptions. Bug 14176 is about http://www.whatwg.org/C#creating-scripts i.e. compile errors. uncaught exception: <script>throw(1)</script> compile error: <script>for(;)</script> 59559 7 ian 2011-11-03 16:14:03 +0000 I guess they would indeed both require changes once the spec expects arguments passed there. 59856 8 ian 2011-11-10 23:32:08 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see bug 14176 Rationale: Concurred with reporter's comments.