Contact emails
jackst...@chromium.org,dom...@chromium.org,fer...@chromium.org
Explainer
https://github.com/jackbsteinberg/std-toast
(No spec yet)
TAG review
https://github.com/w3ctag/design-reviews/issues/385Summary
Introduces a standard, customizable toast notification HTML element, and a JavaScript API to provide easy use for common cases.
Motivation
Modern web applications have grown in the scale of what actions they can offer, to the point where clear feedback is an essential part of a complete, accessible web experience. Toast UI elements are a common way to provide this feedback, and a variety of libraries exist to provide toasts. Creating a built in toast would allow those libraries to layer their implementations on top, and allow web developers to use a simple, unopinionated toast without having to bring a new library into their project.
Risks
Interoperability and Compatibility
The interoperability risk comes from the potential that other browser vendors don't see the benefit of building this into the web platform. We hope that by implementing and iterating with web developer partners, we will be able to determine the value of this effort and make the benefit clearer.
Firefox: No public signals
Edge: No public signals
Safari: No public signals
Web developers: Positive (previously expressed privately; we've encouraged them to make their interest public on the WICG thread)
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
Yes
Tentative tests are being added in the /std-toast folder of Web Platform tests, and will land alongside toast CLs in Chromium. (None have landed yet, but watch https://wpt.fyi/results/std-toast.)
Link to entry on the 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/CAEYN2j4Ps3F%2B_SxjiP%2BE1SFUaSVO_aG8nBbOcPvsSSxaMdgo3g%40mail.gmail.com.
Contact emails
jackst...@chromium.org,domen...@chromium.org,fer...@chromium.org
--
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/BN6PR13MB16511313CC0650F6E0A0BCE6DFEC0%40BN6PR13MB1651.namprd13.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8aY%3D1PV%2BWjpXjp_DPni854YMYDnomiG%2BQyZ_0Fcw%2BhTA%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/CAEYN2j4Ps3F%2B_SxjiP%2BE1SFUaSVO_aG8nBbOcPvsSSxaMdgo3g%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/0a2d6214-2526-4aff-ba76-6237cc0414bf%40chromium.org.
Hi koos,
The Intent to Implement is the beginning of a discussion with standards forums. There’s no “forcing” involved. See https://twitter.com/yoavweiss/status/1139014302151536640 for more background.
As for your specification suggestions, could you file them as issues (or comment on existing issues) on the proposal repository?
--
1. The proposed <toast> is not just a semantic element; it prescribes styling (placement at the bottom of the viewport, presumably with position: fixed;, overlaying other elements. This goes against the separation of concerns.
2. Semantically, it would be too close to <aside>.
3. I wouldn't know the semantic difference between <toast> and other similar proposals, like <popup>, <modal>, <message> and <notification>.
4. The proposed name is derived from an Android UI pattern and may be difficult to understand for those who don't develop for Android.
5. Toast isn't a universal food; it's known only in some of todays cultures. Avocado & toast jokes are stale in 2019 already, imagine what it feels like to code with them in 5 years, or if you've never had toast.