Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

document.open() seems to incorrectly abort XHR, fetch, and image requests that "are not navigating" #25083

Open
pshaughn opened this issue Dec 4, 2019 · 2 comments
Open

document.open() seems to incorrectly abort XHR, fetch, and image requests that "are not navigating" #25083

pshaughn opened this issue Dec 4, 2019 · 2 comments
Labels
A-content/dom Interacting with the DOM from web content
Projects
web-platform-test failures

Comments

@pshaughn
Copy link
Member

pshaughn commented Dec 4, 2019

This is all non-WebSocket subcases in html/webappapis/dynamic-markup-insertion/opening-the-input-stream/abort.sub.window; we get TIMEOUT in each, which makes sense as the mode of failure since the done step of the test is the onload of the request. WebSocket open requests, tested similarly, are correctly completing.
@pshaughn pshaughn changed the title document.open() seems to incorrectly abort XHR, fetch, and image requests that "are not navigating" document.open() seems to incorrectly abort XHR, fetch, and image requests in various navigation states Dec 4, 2019
@pshaughn pshaughn changed the title document.open() seems to incorrectly abort XHR, fetch, and image requests in various navigation states document.open() seems to incorrectly abort XHR, fetch, and image requests that "are not navigating" Dec 4, 2019
@pshaughn
Copy link
Member Author

pshaughn commented Dec 4, 2019

(back-and-forth name change was because I thought I saw another case that could be merged, but it's distinct)

@pshaughn pshaughn mentioned this issue Dec 4, 2019
Open
@jdm jdm added the A-content/dom Interacting with the DOM from web content label Dec 4, 2019
@jdm jdm added this to To do in web-platform-test failures via automation Dec 4, 2019
@jdm
Copy link
Member

jdm commented Dec 4, 2019

This is almost certainly triggered by this code.

@pshaughn pshaughn mentioned this issue Jan 27, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-content/dom Interacting with the DOM from web content
Projects
web-platform-test failures
  
To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jdm @pshaughn