Contact emails
rah...@microsoft.com, jungke...@microsoft.com, cmum...@google.com, raya...@chromium.org
Explainer
Spec
W3C spec: https://w3c.github.io/manifest/#shortcuts-member
Tag Review: https://github.com/w3ctag/design-reviews/issues/510
Summary
This feature provides PWA developers the ability to show a shortcuts menu of common tasks in their app. The menu can be invoked by right clicking the app icon in the quick launch bar after the PWA has been installed on the user’s desktop, or long pressing on the app on Android. This capability already exists for native apps on various platforms (Android, Linux, macOS, and Windows).
Link to “Intent to Prototype” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gK4XF2vbvf0
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The feature will not be supported on WebView since web apps don't exist in that context. The feature will initially be enabled on Android, with support for Desktop platforms to follow.
Demo link
For Android, it needs to be installed via an unstable Chrome channel (canary/dev/beta).
For Windows, the kDesktopPWAsAppIconShortcutsMenu flag needs to be enabled.
Risks
Interoperability and Compatibility
No Interoperability/Compatibility risk. When a web developer doesn’t provide a shortcuts member in the PWA’s WebAppManifest, current installation behavior is not affected by this feature.
Edge: In development/Public Support
Firefox: No signals
Safari: No signals
Web / Framework developers: Positive feedback from web developers
Ergonomics
Shortcuts will be used as part of the WebAppManifest. Use will not affect performance.
Activation
Use will be straightforward, it will only require developers to list their shortcuts in their manifest.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
No, app manifest features are not testable via wpt.
Entry on the feature dashboard
Contact emails
rah...@microsoft.com, jungke...@microsoft.com, cmum...@google.com, raya...@chromium.org
Explainer
Spec
W3C spec: https://w3c.github.io/manifest/#shortcuts-member
Tag Review: https://github.com/w3ctag/design-reviews/issues/510
Summary
This feature provides PWA developers the ability to show a shortcuts menu of common tasks in their app. The menu can be invoked by right clicking the app icon in the quick launch bar after the PWA has been installed on the user’s desktop, or long pressing on the app on Android. This capability already exists for native apps on various platforms (Android, Linux, macOS, and Windows).
Link to “Intent to Prototype” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gK4XF2vbvf0
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The feature will not be supported on WebView since web apps don't exist in that context. The feature will initially be enabled on Android, with support for Desktop platforms to follow.
Demo link
For Android, it needs to be installed via an unstable Chrome channel (canary/dev/beta).
For Windows, the kDesktopPWAsAppIconShortcutsMenu flag needs to be enabled.
Risks
Interoperability and Compatibility
No Interoperability/Compatibility risk. When a web developer doesn’t provide a shortcuts member in the PWA’s WebAppManifest, current installation behavior is not affected by this feature.
Edge: In development/Public Support
Firefox: No signals
Safari: No signals
Web / Framework developers: Positive feedback from web developers
Ergonomics
Shortcuts will be used as part of the WebAppManifest. Use will not affect performance.
Activation
Use will be straightforward, it will only require developers to list their shortcuts in their manifest.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
No, app manifest features are not testable via wpt.
--
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/CAAe2mZ26mswsuxv8ZQ5d%2BEAzBR%3Di%2BJKT3PGbKwA%2BdMprfu24Mw%40mail.gmail.com.
FWIW, https://github.com/mozilla/standards-positions/issues/338 seems promising, although we should let it play out.
Have we considered the "super cookie" issues raised there? Are there mitigations in place against that?
Have we reached out?
Links?
Have we filed a WPT issue that will enable such testing?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ2R3MyC4NHEipHX81bi281wr%2Bi4recLXNB%3Dtus1%2BdRVfQ%40mail.gmail.com.
LGTM1
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ26mswsuxv8ZQ5d%2BEAzBR%3Di%2BJKT3PGbKwA%2BdMprfu24Mw%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+unsubscribe@chromium.org.
LGTM1
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/CAAe2mZ26mswsuxv8ZQ5d%2BEAzBR%3Di%2BJKT3PGbKwA%2BdMprfu24Mw%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/fa3dbffa-f4b5-49ee-a429-90d4d58a242bn%40chromium.org.