navigation.activation stores state about when the current Document was activated (e.g., when it was initialized, or restored from the back/forward cache).
None
This is a cross-document (navigation) feature, so designing it we needed to take care of cross-origin navigation related risks. Since `navigation.activation` is part of the navigation API, it uses the same semantics and protections. We only expose things that are otherwise exposed by the navigation API or in other means.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
It's a web-API, exposing it gradually doesn't make sense.
Shipping on desktop | 123 |
Shipping on Android | 123 |
Shipping on WebView | 123 |
Shipping on WebView | 123 |
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).
NoneRequires code in //chrome?
FalseEstimated milestones
Shipping on desktop 123
Shipping on Android 123
Shipping on WebView 123
Shipping on WebView 123 Anticipated spec changes
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).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5076557983121408Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACf%3D2LJa-_9cEjMU3Ds660KmW0u_G_M9S1Ah-14gAfk9Qhrp2g%40mail.gmail.comThis 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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZLDnYwfav4o7vMLAWE9o_irDceWxKabqcpBbb4e4byDQ%40mail.gmail.com.
On Fri, Jan 26, 2024 at 4:27 AM Noam Rosenthal <nrose...@chromium.org> wrote:
Summarynavigation.activation stores state about when the current Document was activated (e.g., when it was initialized, or restored from the back/forward cache).
Blink componentBlink>History
TAG reviewhttps://github.com/w3ctag/design-reviews/issues/921
TAG review statusIssues addressed
Risks
Interoperability and CompatibilityNone
Gecko: Positive (https://github.com/mozilla/standards-positions/issues/928)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/282)
Web developers: Positive
Other signals:
SecurityThis is a cross-document (navigation) feature, so designing it we needed to take care of cross-origin navigation related risks. Since `navigation.activation` is part of the navigation API, it uses the same semantics and protections. We only expose things that are otherwise exposed by the navigation API or in other means.
WebView application risksDoes this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
DebuggabilityNone
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 chrome://flagsNavigationActivation
Finch feature nameNone
Non-finch justificationIt's a web-API, exposing it gradually doesn't make sense.
I'm always unsure about this, but I believe "Finch feature name" is the flag you'd put in runtime_enabled_features.json5. It can be used by Finch as a kill-switch in case the feature causes some regression in the wild. For this feature, the chrome:://flags flag isn't there though (correct me if I'm wrong)
See
https://chromium.googlesource.com/chromium/src/+/main/docs/flag_guarding_guidelines.md#when-is-a-flag-required.
The new guidance (since Aug 2022) is to add a flag for ~mostly
everything.
Summarynavigation.activation stores state about when the current Document was activated (e.g., when it was initialized, or restored from the back/forward cache).
TAG review statusIssues addressed
Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5076557983121408
Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACf%3D2LJa-_9cEjMU3Ds660KmW0u_G_M9S1Ah-14gAfk9Qhrp2g%40mail.gmail.com
--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bda4f055-7c7a-4684-b8f3-42ee1cdd786cn%40chromium.org.
LGTM3
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8t7sXaQ%3DcGuQFV0bkHJZqYq4ewRNywdZcEWA_ECph0Qg%40mail.gmail.com.