#1040: Navigation API deferred commit
Discussions
Log in to see TAG-private discussions.
Comment by @domenic Feb 7, 2025 (See Github)
We're planning to slightly expand this proposal with one more method: https://github.com/WICG/navigation-api/pull/279 . (It is quite simple in complexity, consisting of a bunch of error-case checks and then updating the destination URL if all those checks pass.)
Discussed
Mar 1, 2025 (See Github)
Matthew: explainer has been updated...
ACTION: re-review with the updated explainer.
Discussed
Apr 1, 2025 (See Github)
Label was wrong, it's not untriaged.
Discussed
Apr 1, 2025 (See Github)
Matthew: Seems ok, but not enough of an expert to be sure … one point I wanted to point out to an expert, I put a couple of links in the comment … seems good to me, but don't want to be the person responsible for merging … couldn't find statements from other engines Hadley: Can you put a comment on the thread and ask the others for their thoughts? Matthew: Will do
Discussed
Apr 1, 2025 (See Github)
Martin: I was unable to identify concrete problems, the design looks reasonable.
Dan: Why is it formally known as the app history api?
Martin: You're looking at the whole explainer, you need to go down to redirect commit section
Dan: Ok, so it's a minor change to an existing thing. What do you want to do with this?
Martin: I think this one is fine
Dan: So we should give it a thumbs up?
Martin: Yes
Dan: Is there any cross-browser support on this? They haven't really provided any indication of multi-implementer support. What do we know about mutli-implementer suppor?
Martin: we know nothing
Let's just ask about multi-implementer support.
We don't see any issues with this, but we note that you haven't asked other implementations about their intentions about this change. Can we request that you ping them before proceeding?
Martin to post the above.
revisit at plenary and possibly close as satisfied
Comment by @martinthomson Apr 24, 2025 (See Github)
I think that the explainer link is now https://github.com/WICG/navigation-api/blob/main/README.md#redirects-during-deferred-commit (the original anchor is gone).
Comment by @martinthomson Apr 24, 2025 (See Github)
Hi @noamr, We don't see any issues with this, but we note that you haven't asked other implementations about their intentions about this change. Can we request that you ping them before proceeding?
Comment by @noamr Apr 24, 2025 (See Github)
Hi @noamr, We don't see any issues with this, but we note that you haven't asked other implementations about their intentions about this change. Can we request that you ping them before proceeding?
Oh it seems like I forgot to cross-post the standards position back to here: https://github.com/WebKit/standards-positions/issues/449 https://github.com/mozilla/standards-positions/issues/1169
Either way, hanks for the review!
OpenedJan 16, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of "deferred commit" behavior for navigation API.
This is a small extension of the navigation API, which was previously reviewed in https://github.com/w3ctag/design-reviews/issues/605 and https://github.com/w3ctag/design-reviews/issues/717.
Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/navigation-api/blob/main/README.md#deferred-commit User research: Actively discussed on our issue tracker: https://github.com/WICG/navigation-api/issues/277, also requested by major frameworks. Security and Privacy self-review²: None - this shouldn't expose anything that isn't already available GitHub repo (if you prefer feedback filed there): https://github.com/WICG/navigation-api/ Primary contacts (and their relationship to the specification): Nate Chapin (@natechapin), Google Noam Rosenthal (@noamr), Google Domenic Denicola (@domenic), Google Organization/project driving the design: Google External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5134734612496384. Further details: We recognize that this might be too small for TAG to review, but we'd let TAG be the judge of that.
I have reviewed the TAG's Web Platform Design Principles The group where the incubation/design work on this is being done (or is intended to be done in the future): WICG The group where standardization of this work is intended to be done ("unknown" if not known): WHATWG Existing major pieces of multi-stakeholder review or discussion of this design: https://github.com/WICG/navigation-api/issues/225 Major unresolved issues with or opposition to this design: None yet. The main point of debate has been the name. I am happy to consider alternatives to sourceElement. This work is being funded by: Google We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a comment in this issue and @-notify [@natechapin, @domenic, @noamr]