diff --git a/source b/source index 4295662723a..863f66c5f1e 100644 --- a/source +++ b/source @@ -2828,6 +2828,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • inherit
  • interface prototype object
  • implements
    • +
  • associated realm
  • [[Realm]] field of a platform object
  • [[GetOwnProperty]] internal method of a named properties object
  • callback context
    • @@ -59301,9 +59302,7 @@ interface ValidityState { agent may run the focusing steps for element, and may change the scrolling position of the document, or perform some other action that brings element to the user's attention. User agents may report more than one constraint violation, if - element suffers from multiple problems at once. If element is not - being rendered, then the user agent may, instead of notifying the user, - report the error for the running script.

    + element suffers from multiple problems at once.

  • Return false.

    • @@ -72937,16 +72936,30 @@ customElements.define("x-foo", class extends HTMLElement {
    upgrade reaction
    -
    Upgrade element using - reaction's custom element definition.
    +
    +

    Upgrade element using + reaction's custom element definition.

    + +

    If this throws an exception, catch it, and report it for reaction's custom element + definition's constructor's corresponding + JavaScript object's realm's global + object.

    +
    callback reaction
    -
    Invoke reaction's - callback function with reaction's arguments, and with element as the - callback this value.
    +
    +

    Invoke reaction's + callback function with reaction's arguments, and with element as + the callback this value.

    + +

    If this throws an exception, catch it, and report it for reaction's callback function's corresponding + JavaScript object's realm's global + object.

    +
    - -

    If this throws an exception, catch it, and report the exception.

    @@ -93688,17 +93701,10 @@ const p2 = navigation.navigate(url2).finished; event to null.

  • -

    Fire an event named navigateerror at navigation using - ErrorEvent, with error initialized to - error, and message, filename, lineno, and colno initialized to appropriate values - that can be extracted from error and the current JavaScript stack in the same - underspecified way that the report the exception algorithm does.

    +

    Let errorInfo be the result of extracting error + information from error.

    -

    Thus, for example, if this algorithm is reached because of a call to For example, if this algorithm is reached because of a call to window.stop(), these properties would probably end up initialized based on the line of script that called window.stop(). But if it's because the user clicked the stop @@ -93706,6 +93712,11 @@ const p2 = navigation.navigate(url2).finished; 0.

    • +

  • Fire an event named navigateerror at navigation using + ErrorEvent, with additional attributes initialized according to + errorInfo.

    • +

  • If navigation's ongoing API method tracker is non-null, then reject the finished promise for apiMethodTracker with error.

    • @@ -95009,15 +95020,13 @@ interface NavigationDestination {

  • Finish event given false.

    • +

  • Let errorInfo be the result of extracting error + information from rejectionReason.

    • +

  • Fire an event named navigateerror at navigation using - ErrorEvent, with error initialized to - rejectionReason, and message, filename, lineno, and colno initialized to appropriate - values that can be extracted from rejectionReason in the same underspecified way - that the report the exception algorithm does.

    + ErrorEvent, with additional attributes initialized according to + errorInfo.

  • If navigation's transition is not null, then reject @@ -105462,6 +105471,9 @@ new PaymentRequest(…); // Allowed to use object">the environment settings object's global object.

    • +

    A global object has an in error reporting mode + boolean, which is initially false.

    +

    To create a new realm in an agent agent, optionally with instructions to create a global object or a global this binding (or both), the following steps are taken:

    @@ -107552,8 +107564,9 @@ document.querySelector("button").addEventListener("click", bound);

    Otherwise, rethrow errors is false. Perform the following steps:

      -

    1. Report the exception given by evaluationStatus.[[Value]] for - script.

      2. +

    2. Report an exception given by evaluationStatus.[[Value]] for + script's settings object's + global object.

    3. Clean up after running script with settings.

      4. @@ -107618,8 +107631,9 @@ document.querySelector("button").addEventListener("click", bound);

    4. If preventErrorReporting is false, then upon rejection of - evaluationPromise with reason, report the exception given by - reason for script.

      5. + evaluationPromise with reason, report an exception given by + reason for script's settings + object's global object.

    5. Clean up after running script with settings.

      6. @@ -107734,99 +107748,154 @@ document.querySelector("button").addEventListener("click", bound);
      -

      When the user agent is required to report an error for a - particular script script with a particular - position line:col, using a particular target target, it must run these steps, after which the error is either handled or not - handled:

      +

      To extract error information from a JavaScript value + exception:

        -

      1. If target is in error reporting mode, then return; the error is not handled.

        2. +

      2. Let attributes be an empty map keyed by IDL + attributes.

        3. -

      3. Let target be in error reporting mode.

        4. +

      4. Set attributes[error] to + exception.

        5. -

      5. - - Let message be an implementation-defined string describing the error in a - helpful manner.

        6. +
      6. +

        + + Set attributes[message], + attributes[filename], + attributes[lineno], and + attributes[colno] to + implementation-defined values derived from exception. +

        + +

        Browsers implement behavior not specified here or in the JavaScript + specification to gather values which are helpful, including in unusual cases (e.g., eval). In the future, this might be specified in greater detail.

        +
        7. -

      7. Let errorValue be the value that represents the error: in the case of an - uncaught exception, that would be the value that was thrown; in the case of a JavaScript error - that would be an Error object. If there is no corresponding value, then - the null value must be used instead.

        8. +

      8. Return attributes.

        9. +
      -
    6. -

      Let urlString be the result of applying the URL serializer to the URL record that - corresponds to the resource from which script was obtained.

      +

      To report an exception exception which is a JavaScript value, for a + particular global object global and optional boolean omitError (default false):

      -

      The resource containing the script will typically be the file from which the - Document was parsed, e.g. for inline script elements or event - handler content attributes; or the JavaScript file that the script was in, for external - scripts. Even for dynamically-generated scripts, user agents are strongly encouraged to attempt - to keep track of the original source of a script. For example, if an external script uses the - document.write() API to insert an inline - script element during parsing, the URL of the resource containing the script would - ideally be reported as being the external script, and the line number might ideally be reported - as the line with the document.write() call or where the - string passed to that call was first constructed. Naturally, implementing this can be somewhat - non-trivial.

      +
        +

      1. Let notHandled be true.

        2. + +

      2. Let errorInfo be the result of extracting error + information from exception.

        3. + +
      3. +

        Let script be a script found in an + implementation-defined way, or null. This should usually be the running + script (most notably during run a classic script).

        -

        User agents are similarly encouraged to keep careful track of the original line - numbers, even in the face of document.write() calls - mutating the document as it is parsed, or event handler content attributes spanning - multiple lines.

        +

        Implementations have not yet settled on interoperable behavior for which script + is used to determine whether errors are muted in less common cases.

      4. If script is a classic script and script's muted - errors is true, then set message to "Script error.", - urlString to the empty string, line and col to 0, and - errorValue to null.

        5. + errors is true, then set errorInfo[error] to null, errorInfo[message] to "Script error.", + errorInfo[filename] to the empty + string, errorInfo[lineno] to 0, and + errorInfo[colno] to 0.

        -

      5. Let notHandled be true.

        6. +

      6. If omitError is true, then set errorInfo[error] to null.

        7. + +
      7. +

        If global is not in error reporting mode, then:

        -

      8. If target implements EventTarget, then set notHandled - to the result of firing an event named error at target, using ErrorEvent, with the - cancelable attribute initialized to true, the message attribute initialized to message, the - filename attribute initialized to - urlString, the lineno attribute - initialized to line, the colno attribute - initialized to col, and the error attribute - initialized to errorValue.

        9. +
          +
        1. Set global's in error reporting mode to true.
          2. -

        2. Let target no longer be in error reporting mode.

          3. +
        3. +

          If global implements EventTarget, then set notHandled to + the result of firing an event named error at global, using ErrorEvent, with + the cancelable attribute initialized to true, + and additional attributes initialized according to errorInfo.

          + +

          Returning true in an event handler cancels the event per the event + handler processing algorithm.

          +
          4. + +

        4. Set global's in error reporting mode to false.

          5. +
        +
      9. -

        If notHandled is false, then the error is handled. Otherwise, the error is not handled.

        +

        If notHandled is true, then:

        + +
          +

        1. Set errorInfo[error] to + null.

          2. + +
        2. +

          If global implements DedicatedWorkerGlobalScope, queue a + global task on the DOM manipulation task source with the + global's associated Worker's relevant global object to + run these steps:

          + +
            +

          1. Let workerObject be the Worker object associated with + global.

            2. + +

          2. Set notHandled be the result of firing + an event named error at workerObject, + using ErrorEvent, with the cancelable attribute initialized to true, + and additional attributes initialized according to errorInfo.

            3. -

            Returning true in an event handler cancels the event per the event handler - processing algorithm.

            +
          3. +

            If notHandled is true, then report + exception for workerObject's relevant global object with + omitError set to true.

            + +

            The actual exception value will not be available in the owner + realm, but the user agent still carries through enough information to set the message, + filename, and other attributes, as well as potentially report to a developer console.

            +
            4. +
          +
          3. +
        10. + +

      10. Otherwise, the user agent may report exception to a developer console.

      -

      When the user agent is to report an exception - E, the user agent must report the error for the relevant 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 a developer console.

      +

      If the implicit port connecting a worker to its Worker object has been + disentangled (i.e. if the parent worker has been terminated), then the user agent must act as if + the Worker object had no error event handler and as + if that worker's onerror attribute was + null, but must otherwise act as described above.

      + +

      Thus, error reports propagate up to the chain of dedicated workers up to the + original Document, even if some of the workers along this chain have been terminated + and garbage collected.

      -

      The existence of both report an error and - report an exception is confusing, and both algorithms - have known problems. You can track future cleanup in this area in issue #958.

      +

      Previous revisions of this standard defined an algorithm to report the exception. As part of issue #958, this has been superseded by report an + exception which behaves differently and takes different inputs. Issue #10516 tracks updating the + specification ecosystem.

      + +

      The reportError(e) method steps are to - report the exception e.

      + report an exception e for this.

      + +

      It is unclear whether muting is + applicable here. In Chrome and Safari it is muted, but in Firefox it is not. See also issue #958.

      + +

      The ErrorEvent interface is defined as follows:

      @@ -107931,12 +108000,9 @@ dictionary ErrorEventInit : EventInit {

      This algorithm results in promise rejections being marked as handled or not handled. These concepts parallel - handled and not - handled script errors. If a rejection is still not handled after this, then the rejection may - be reported to a developer console.

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

      The PromiseRejectionEvent interface is defined as follows:

      @@ -108007,13 +108073,10 @@ dictionary PromiseRejectionEventInit : EventInitimport map parse result result:

        -

      1. If result's error to rethrow is - not null, then report the exception given by result's error to rethrow and return.

        2. + not null, then report an exception given by result's error to rethrow for global and + return.

      2. Assert: global's import map is an empty import map.

        3. @@ -109118,7 +109181,8 @@ dictionary PromiseRejectionEventInit : EventInit

        Clean up after running script with entry.

      3. If result is an abrupt completion, - then report the exception given by result.[[Value]].

        4. + then report an exception given by result.[[Value]] for + global.

    @@ -109168,6 +109232,12 @@ dictionary PromiseRejectionEventInit : EventInitpromise.then(null, null). For the latter, it is because a revoked Proxy was passed. In both cases, all the steps below that would otherwise use job settings get skipped.

    + +

    NewPromiseResolveThenableJob + and NewPromiseReactionJob + both seem to provide non-null realms (the current Realm Record) in the case of a revoked + proxy. The previous text could be updated to reflect that.

    @@ -109202,8 +109272,21 @@ dictionary PromiseRejectionEventInit : EventInit

    If job settings is not null, then clean up after running script with job settings.

    -

  • If result is an abrupt completion, - then report the exception given by result.[[Value]].

    • +
  • +

    If result is an abrupt completion, then + report an exception given by result.[[Value]] for realm's + global object.

    + +

    There is a very gnarly case where HostEnqueuePromiseJob is called with a null + realm (e.g., because Promise.prototype.then was called with null handlers) but also the job + returns abruptly (because the promise capability's resolve or reject handler threw, possibly + because this is a subclass of Promise that takes the supplied functions and wraps them in + throwing functions before passing them on to the function passed to the Promise superclass + constructor. Which global is to be used then, considering that the current realm could be + different at each of those steps, by using a Promise constructor or Promise.prototype.then + from another realm? See issue + #10526.

    +
    • @@ -111420,7 +111503,7 @@ import "https://example.com/foo/../module2.mjs";

    If an exception gets thrown by the callback, end these steps and allow the exception to propagate. (It will propagate to the DOM event dispatch - logic, which will then report the exception.)

    + logic    , which will then report it.)

  • @@ -111601,12 +111684,14 @@ typedef OnBeforeUnloadEventHandlerNonNull? OnBeforeUnl the event handler's listener (if present).

    • -

  • Report the error for the appropriate script and with the appropriate position (line number and - column number) given by location, using settings object's global object. If the error is still not handled after this, then the error may be reported - to a developer console.

    • +

  • Let syntaxError be a new SyntaxError exception associated + with settings object's realm which describes the error while parsing. It should be based on + location, where the script body originated.

    • + +

  • Report an exception with syntaxError + for settings object's global + object.

  • Return null.

    • @@ -113583,11 +113668,18 @@ enum DOMParserSupportedType {

  • Record timing info for timer handler given handler, global's relevant settings object, and repeat.

    • -

  • If handler is a Function, then invoke handler given - arguments with the callback this - value set to thisArg. If this throws an exception, catch it, and - report the exception.

    • +
  • +

    If handler is a Function, then invoke handler given + arguments with the callback this + value set to thisArg. If this throws an exception, catch it, and report it for handler's corresponding + JavaScript object's associated realm's global object.

    + +

    This global object not necessarily the same as global, if + handler comes from another realm.

    +

  • Otherwise:

    @@ -113620,7 +113712,8 @@ enum DOMParserSupportedType {

  • Perform EnsureCSPDoesNotBlockStringCompilation(realm, « », handler, handler, timer, « », handler). If this throws - an exception, catch it, report the exception, and abort these steps.

    • + an exception, catch it, report it for + global, and abort these steps.

  • Let settings object be global's relevant settings @@ -113831,8 +113924,12 @@ scheduleWork(); // queues a task to do lots of work

    The queueMicrotask(callback) method must queue a microtask to invoke - callback, and if callback throws an exception, report the - exception.

    + callback, and if callback throws an exception, report it for callback's corresponding JavaScript object's + associated realm's global object.

    + +

    This global object not necessarily the same as this, if + callback comes from another realm.

    The queueMicrotask() method allows authors to schedule a callback on the microtask queue. This allows their code to run once the @@ -115971,7 +116068,11 @@ interface mixin AnimationFrameProvider {

  • Invoke callback, passing now as the only argument, and if an exception is thrown, - report the exception.

    • + report it for callback's + corresponding JavaScript object's associated realm's + global object.

    +

    This global object not necessarily the same as this, if + callback comes from another realm.

    @@ -119200,52 +119301,8 @@ interface SharedWorkerGlobalScope : WorkerGlobalScope

    Runtime script errors

    Whenever an uncaught runtime script error occurs in one of the worker's scripts, if the error - did not occur while handling a previous script error, the user agent must - will report the error for that script, with the position (line number and column number) where the - error occurred, using the WorkerGlobalScope object as the target.

    - -

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

    - -

    For dedicated workers, if the error is still not - handled afterwards, the error report propagates to the Worker object, - then to any containing workers in the same fashion, eventually reaching the Window if - it was never handled along the way.the user agent must queue a - task to run these steps:

    - -
    - -
      -

    1. Let notHandled be the result of firing an - event named error at the Worker object - associated with the worker, using ErrorEvent, with the cancelable attribute initialized to true, the message, filename, lineno, and colno attributes initialized appropriately, and the error attribute initialized to null.

      2. - -

    2. If notHandled is true, then the user agent must act as if the uncaught runtime - script error had occurred in the global scope that the Worker object is in, thus - repeating the entire runtime script error reporting process one level up.

      3. -
    - -

    If the implicit port connecting the worker to its Worker object has been - disentangled (i.e. if the parent worker has been terminated), then the user agent must act as if - the Worker object had no error event handler and as - if that worker's onerror attribute was - null, but must otherwise act as described above.

    - -
    - -

    Thus, errorError reports propagate up to - the chain of dedicated workers up to the original Document, even if some of the - workers along this chain have been terminated and garbage collected.

    - -

    The task source for the task mentioned above is the DOM manipulation - task source.

    + did not occur while handling a previous script error, the user agent will report it for the worker's WorkerGlobalScope object.

    Creating workers

    @@ -128244,10 +128301,11 @@ document.body.appendChild(text);

    1. Attach a shadow root with declarative shadow host element, mode, clonable, - serializable, delegatesFocus, and "named". - If an exception is thrown, then catch it, report the exception, - insert an element at the adjusted insertion location with - template, and return.

      2. + serializable, delegatesFocus, and "named". If + an exception is thrown, then catch it, report it + for declarative shadow host element's relevant global object, + insert an element at the adjusted insertion location with template, + and return.

    2. Let shadow be declarative shadow host element's shadow root.