This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/timers.html Multipage: http://www.whatwg.org/C#get-the-timed-task Complete: http://www.whatwg.org/c#get-the-timed-task Comment: For setTimeout("{", 10) we think window.onerror's second argument should be "" 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
Actually, scrap that. Use the caller's location, unless that's a different origin in which case the arguments should be "Script error.", "", 0
Can you elaborate?
When a script calls setTimeout (or setInterval) and the first argument is a string, then let the created script use the same script URL as the script that called the method, so window.onerror's second argument is set correctly in case of a compile error or runtime error.
As in bug 14176, this basically means giving the "report an error" algorithm explicit arguments to use for onerror's arguments, instead of allows the UAs to do whatever they want here.
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.