Skip to content

Commit

Permalink
Do not fire error events on inactive globals
Browse files Browse the repository at this point in the history
That is, on globals whose responsible document is not fully active.
Discussed in #1956.
  • Loading branch information
domenic committed Oct 31, 2016
1 parent 5454d70 commit 5d66b71
Showing 1 changed file with 8 additions and 3 deletions.
11 changes: 8 additions & 3 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -87431,15 +87431,20 @@ document.querySelector("button").addEventListener("click", bound);

<p>When the user agent is required to <dfn data-x="report the error">report an error</dfn> for a
particular <span data-x="concept-script">script</span> <var>script</var> with a particular
position <var>line</var>:<var>col</var>, using a particular target <var>target</var>, it must run these steps, after which the error is either <dfn
data-x="concept-error-handled"><i>handled</i></dfn> or <dfn data-x="concept-error-nothandled"><i>not
handled</i></dfn>:</p>
position <var>line</var>:<var>col</var>, using a particular target <span>global object</span>
<var>target</var>, it must run these steps, after which the error is either <dfn
data-x="concept-error-handled"><i>handled</i></dfn> or <dfn
data-x="concept-error-nothandled"><i>not handled</i></dfn>:</p>

<ol>

<li><p>If <var>target</var> is <span>in error reporting mode</span>, then abort these
steps; the error is <i data-x="concept-error-nothandled">not handled</i>.</p></li>

<li><p>If <var>target</var>'s <span>responsible <code>Document</code></span> is not <span>fully
active</span>, then abort these steps; the error is <i data-x="concept-error-nothandled">not
handled</i>.</p></li>

<li><p>Let <var>target</var> be <dfn>in error reporting mode</dfn>.</p></li>

<li><p>Let <var>message</var> be a user-agent-defined string describing the error in a
Expand Down

0 comments on commit 5d66b71

Please sign in to comment.