Intent to Extend Origin Trial: Badging API
ray...@google.com
Contact emails
ray...@chromium.org, domi...@chromium.org, harr...@chromium.org
Spec
Draft: https://wicg.github.io/badging
Summary
Allows web applications (as defined by the Web App Manifest standard) to set an application-wide badge, shown in an operating-system-specific place associated with the application (such as the shelf or home screen). The badge can optionally show a positive integer over the top of the application icon.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/d/msg/blink-dev/Fw764MVF5nI/FNlBi815AwAJ
Goals for experimentation
During the open-for-comments period (since the I2I), we have received a number of bug reports asking for changes to the API surface, which are summarized in this doc:
https://github.com/WICG/badging/blob/master/choices.md
We’d like to receive a wider range of input on the current API design before we make changes, since these suggestions are not obviously improvements.
Experimental timeline
We'd like to run the experiment for one more milestone: M76. We have a partner signed up to use the API but we haven't had substantial enough feedback yet. There are no changes to the API.
Any risks when the experiment finishes?
No risk of data loss. However, it would represent a disappearing prominent feature in apps using it. We're planning to rename the API in order to launch it in the milestone following the end of the trial.
Other details can be found on the original intent to experiment: https://groups.google.com/a/chromium.org/d/msg/blink-dev/KEUnHsvulEU/tMzKbzHxBQAJ
Yoav Weiss
Contact emails
ray...@chromium.org, domi...@chromium.org, harr...@chromium.org
Spec
Draft: https://wicg.github.io/badging
Summary
Allows web applications (as defined by the Web App Manifest standard) to set an application-wide badge, shown in an operating-system-specific place associated with the application (such as the shelf or home screen). The badge can optionally show a positive integer over the top of the application icon.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/d/msg/blink-dev/Fw764MVF5nI/FNlBi815AwAJ
Goals for experimentation
During the open-for-comments period (since the I2I), we have received a number of bug reports asking for changes to the API surface, which are summarized in this doc:
https://github.com/WICG/badging/blob/master/choices.mdWe’d like to receive a wider range of input on the current API design before we make changes, since these suggestions are not obviously improvements.
Experimental timeline
We'd like to run the experiment for one more milestone: M76. We have a partner signed up to use the API but we haven't had substantial enough feedback yet. There are no changes to the API.
Any risks when the experiment finishes?
No risk of data loss. However, it would represent a disappearing prominent feature in apps using it. We're planning to rename the API in order to launch it in the milestone following the end of the trial.
Other details can be found on the original intent to experiment: https://groups.google.com/a/chromium.org/d/msg/blink-dev/KEUnHsvulEU/tMzKbzHxBQAJ
--
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/e0eb3d4b-fbec-4f80-8f8f-6d7bb553fd3f%40chromium.org.