[llannasatoll]

This PR updates the spec to invoke the mark navigation conditions as potentially changed abstract operation introduced in whatwg/html#11765 upon client-side cookie (document.cookie and CookieStore) modifications.

• At least two implementers are interested (and none opposed):
  • Chromium (Proposal: Add optimization to ignore "duplicate" navigations html#11743)
  • …
• Tests are written and can be reviewed and commented upon at:
  • https://chromium-review.googlesource.com/c/chromium/src/+/5856811
• Implementation bugs are filed:
  • Chromium: https://crbug.com/366060351
  • Gecko: …
  • WebKit: …
• MDN issue is filed: …
• The top of this comment includes a clear commit message to use.

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

---

💥 Error: 422 Unprocessable Entity 💥

PR Preview failed to build. (Last tried on Oct 20, 2026, 12:52 PM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs

🔗 Related URL

Error output:

[
    {
        "lineNum": "658:45",
        "messageType": "link",
        "text": "No 'dfn' refs found for 'mark navigation conditions as potentially changed'."
    },
    {
        "lineNum": null,
        "messageType": "failure",
        "text": "Did not generate, due to errors exceeding the allowed error level."
    }
]

This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!

If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.

[DCtheTall]

This feature seems to apply to all cookies, not just the Cookie Store API. It probably makes sense to update the spec in one place where the cookie storage model is invoked.

@annevk I think this type of thing belongs in Fetch when we move more of the cookie spec into that. The flag in this feature would be a side effect of Cookie Store API calling methods in the Fetch spec, since I do not see a reason this API needs to be aware of this flag. WDYT?

[annevk]

I think it's just cookie APIs (so this and document.cookie) that can cause this flag to be set. Not anything network-based. If that's correct having it here might be okay, though perhaps we should still have an abstraction that all APIs can use that takes care of this.

[llannasatoll]

I'm sorry for the long delay. I now have updated the PR to invoke the new mark navigation conditions as potentially changed abstract operation defined in whatwg/html#11765. This removes the need for the Cookie Store API to manually inspect the Window and Document navigable flags. Could you take another look?

[DCtheTall]

lgtm, thanks for your contribution and apologies for the delay myself 😄