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.

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

Make it explicit that user agents can ignore replaceState/pushState #999

Merged
merged 2 commits into from
Apr 6, 2016

Conversation

domenic
Copy link
Member

@domenic domenic commented Apr 5, 2016

Fixes #982. The "a user agent could ignore calls" is moved from the
non-normative implementation notes to the normative algorithm, and the
implementation notes are updated with a pointer to this.

@beidson, can you review?

@domenic domenic added the clarification Standard could be clearer label Apr 5, 2016
listeners that are not triggered in response to a clear user action, or that are invoked in rapid
succession.</p>
<p>For both <code data-x="dom-history-pushState">pushState()</code> and <code
data-x="dom-history-replaceState">replaceState()</code>, user agents should be careful to prevent
Copy link
Member

Choose a reason for hiding this comment

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

Since this appears in a non-normative section, we cannot use should.

@beidson
Copy link

beidson commented Apr 6, 2016

Lgtm, except for what @annevk already noted.

It should be next to the other session history stuff.
Fixes #982. The "a user agent could ignore calls" is moved from the
non-normative implementation notes to the normative algorithm, and the
implementation notes are updated with a pointer to this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: history
Development

Successfully merging this pull request may close these issues.

3 participants