This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14177 - onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0)
Summary: onerror: If the script is not same-origin, window.onerror should be invoked w...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-16 07:06 UTC by contributor
Modified: 2011-11-10 23:32 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-09-16 07:06:24 UTC 
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
Comment 1 Ms2ger 2011-09-16 14:51:07 UTC 

*** This bug has been marked as a duplicate of bug 14176 ***
Comment 2 Simon Pieters 2011-09-16 17:02:40 UTC 
It's not a dup (affects different part of the spec)
Comment 3 Ian 'Hixie' Hickson 2011-10-19 23:20:12 UTC 
Could you elaborate?
Comment 4 Simon Pieters 2011-10-20 21:48:01 UTC 
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).
Comment 5 Ian 'Hixie' Hickson 2011-10-26 23:57:30 UTC 
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?
Comment 6 Simon Pieters 2011-10-27 08:23:38 UTC 
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>
Comment 7 Ian 'Hixie' Hickson 2011-11-03 16:14:03 UTC 
I guess they would indeed both require changes once the spec expects arguments passed there.
Comment 8 Ian 'Hixie' Hickson 2011-11-10 23:32:08 UTC 
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.