When a navigation is initiated by an Element (i.e., a link click or a form submission), the sourceElement property on the NavigateEvent will be the initiating element.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
Coverage throughout the navigation-api/ WPT suite: https://chromium-review.googlesource.com/c/chromium/src/+/4385906
Shipping on desktop | 135 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
NoneContact emails jap...@chromium.org, dom...@chromium.org, nrose...@chromium.org
Explainer https://github.com/WICG/navigation-api/commit/85edaf1d4d42355b020807cd56f6a22784978c3d
Specification https://html.spec.whatwg.org/multipage/nav-history-apis.html#dom-navigateevent-sourceelement
SummaryWhen a navigation is initiated by an Element (i.e., a link click or a form submission), the sourceElement property on the NavigateEvent will be the initiating element.
Blink component Blink>History
TAG review
--
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 blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/428b7dd4-add0-4c07-8dbd-214c90515dabn%40chromium.org.
LGTM3