Skip to content

"Wait for navigation to complete" Step 2.2 and page loading strategy "none" #795

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.

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

Closed
vkatsikaros opened this issue Feb 22, 2017 · 3 comments
Assignees
Milestone

Comments

@vkatsikaros
Copy link
Contributor

I apologize if I have completely missed the answer from other parts of the spec.

In definition wait for navigation to complete:

2.1 Let readiness target be the document readiness state tied to the current session’s page loading strategy, which can be found in the table of page load strategies.

2.2 Wait for the the current browsing context’s document readiness state to reach readiness target, or for the session page load timeout to pass, whichever occurs sooner.

When the page loading strategy is "none", the document readiness state is not defined (or it's equal to an empty string?) in the table of page load strategies.

My question is what it means for document readiness state to reach the readiness target when the page loading strategy is "none".

@shs96c
Copy link
Contributor

shs96c commented Feb 22, 2017

Any document readiness state is acceptable when page loading strategy is none --- we don't bother checking it, and just return ASAP.

@shs96c shs96c modified the milestone: Level 1 Feb 22, 2017
@shs96c shs96c self-assigned this Feb 22, 2017
@andreastt
Copy link
Member

When we have no page loading strategy, we should avoid comparing the document’s ready state.

@shs96c
Copy link
Contributor

shs96c commented Mar 1, 2017

Fixed in 87fc501

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants