From ede210589893ce4ef636d7d41f7665fd75fb9eba Mon Sep 17 00:00:00 2001 From: Domenic Denicola Date: Wed, 23 Dec 2015 19:36:07 -0500 Subject: [PATCH] Report errors to developer consoles, not users In #224 we had a brief discussion which concluded that these statements about error reporting really referred to a developer console. Alternately, maybe they are holdovers from the early days of the web when browsers did in fact show popups with every JavaScript error. Regardless, this uniformly updates all script error reporting to be to a developer console, instead of to the user. --- source | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source b/source index 479e0a02011..c42beb5c93e 100644 --- a/source +++ b/source @@ -86275,8 +86275,8 @@ interface NavigatorOnLine { data-x="concept-script">script, with the problematic position (line number and column number) in the resource containing the script, using the global object specified by the script's settings object as the target. If the error is still not handled after this, then the error may be reported to - the user.

+ data-x="concept-error-nothandled">not handled after this, then the error may be reported to a + developer console.

The ErrorEvent interface
@@ -87323,7 +87323,7 @@ typedef OnBeforeUnloadEventHandlerNonNull? OnBeforeUnloadEvent column number) given by location, using the global object specified by script settings as the target. If the error is still not handled after this, then the error may be reported - to the user.

+ to a developer console.

  • Return null.

    • @@ -95162,7 +95162,7 @@ interface WorkerGlobalScope : EventTarget { the target.

    For shared workers, if the error is still not handled - afterwards, the error may be reported to the user.

    + afterwards, the error may be reported to a developer console.

    For dedicated workers, if the error is still not handled afterwards, the user agent must queue a task to