Skip to content

Conversation

@domenic
Copy link
Member

@domenic domenic commented May 25, 2021

  • Makes the discussion of user agent interface invoke "stop document loading", not "abort a document", since the browser stop button also cancels ongoing navigations.

  • Remove the "should" suggestion to fire an abort event. Closes "abort" Event Isn't Fired When Aborting Document Load #3525. Since this was the only case where abort was fired, this removes the event definition and event handler content attribute definition, effectively making use of the onabort="" content attribute nonconforming. (But, we keep the IDL definition in GlobalEventHandlers and the associated mapping.)

  • Tweaks the active document check in "stop document loading" to be more correct.

/cc @jgraham since he's been looking at the specs for high-level "UI actions" recently.

  • At least two implementers are interested (and none opposed):
    • This matches all browsers
  • Tests are written and can be reviewed and commented upon at:
    • I don't know if there's a webdriver mechanism for pressing the stop button, but that would be necessary for tests.
  • Implementation bugs are filed:
    • Chrome: N/A
    • Firefox: N/A
    • Safari: N/A

(See WHATWG Working Mode: Changes for more details.)


/browsing-the-web.html ( diff )
/dom.html ( diff )
/indices.html ( diff )
/webappapis.html ( diff )

* Makes the discussion of user agent interface invoke "stop document loading", not "abort a document", since the browser stop button also cancels ongoing navigations.

* Remove the "should" suggestion to fire an abort event. Closes #3525. Since this was the only case where abort was fired, this removes the event definition and event handler content attribute definition, effectively making use of the onabort="" content attribute nonconforming. (But, we keep the IDL definition in GlobalEventHandlers and the associated mapping.)

* Tweaks the active document check in "stop document loading" to be more correct.
@domenic domenic added removal/deprecation Removing or deprecating a feature topic: navigation impacts documentation Used by documentation communities, such as MDN, to track changes that impact documentation labels May 25, 2021

<!-- I'd love to make this more precise, anyone have any suggestions on what it should say? -->
<p>User agents may allow users to explicitly invoke the <span>stop document loading</span> for a
<code>Document</code>.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Including nested documents? I suppose browsers only offer this for the top-level?

Copy link
Member Author

@domenic domenic May 26, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can do it using the context menu in Firefox, although apparently not Chrome: https://boom-bath.glitch.me/slow-subframe-outer.html

(in Chrome the context menu continues to say "Reload" even while a document is loading.)

@domenic
Copy link
Member Author

domenic commented May 26, 2021

I double-checked by source inspection that all three engines still have onabort in GlobalEventHandlers, despite never firing it.

@domenic domenic merged commit f67b46d into main May 26, 2021
@domenic domenic deleted the stop-button branch May 26, 2021 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impacts documentation Used by documentation communities, such as MDN, to track changes that impact documentation removal/deprecation Removing or deprecating a feature topic: navigation

Development

Successfully merging this pull request may close these issues.

"abort" Event Isn't Fired When Aborting Document Load

3 participants