Contact emails
[email protected]

Explainer
https://github.com/WICG/navigation-api/pull/294


Specification
https://html.spec.whatwg.org/#dom-navigationprecommitcontroller-addhandler


Summary
Currently when intercepting navigations with the `navigate` event, 
precommitHandlers and post-commit ordinary handlers are passed separately. This 
works well when there is only one or the other, but can be a bit clunky when 
the flow includes a precommitHandler that leads to a post-commit handler. This 
addition is a small ergonomic improvement that enables registering a 
post-commit handler while invoking a precommit handler.


Blink component
Blink>DOM


Web Feature ID
navigation


Motivation
This is a small ergonomic fix to the API enabling a bit more flexibility.


Initial public proposal
https://github.com/whatwg/html/issues/11956


TAG review
No information provided


TAG review status
Pending


Risks




Interoperability and Compatibility
None, new API

Gecko: No signal

WebKit: No signal

Web developers: Positive This was initially raised by Jake Archibald when at 
Shopify.

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?
No information provided



Debuggability
No information provided


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
Yes


Is this feature fully tested by web-platform-tests?
Yes



Flag name on about://flags
No information provided


Finch feature name
NavigateEventAddHandlerOnPrecommit


Rollout plan
Will ship enabled for all users


Requires code in //chrome?
False


Tracking bug
https://issues.chromium.org/issues/465487215


Estimated milestones


Shipping on desktop 147

Shipping on Android 147

Shipping on WebView 147




Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (eg links to known github issues in the project 
for the feature specification) whose resolution may introduce web 
compat/interop risk (eg, changing to naming or structure of the API in a 
non-backward-compatible way).
No information provided


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5176907844943872?gate=6492610946531328


This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6981eba6.050a0220.baa59.00f7.GAE%40google.com.

Reply via email to