On Tue, Jul 1, 2025 at 9:56 PM Diego Gonzalez <luigo...@microsoft.com> wrote:
> > > Hola Dominic, > > This was generated through a link to a doc > <https://docs.google.com/document/d/1vlTlsQKThwaX0-lj_iZbVTzyqY7LioqERU8DK3u3XjI/edit?tab=t.0#bookmark=id.pygli2e122ic> > in > the process documentation > <https://www.chromium.org/blink/launching-features/#origin-trials>. > Sorry, I hovered over all the links I could find nearby the section you linked in "process documentation", and wasn't able to find anything linking to that doc. Can you be a bit more specific, so that we can remove all references to this document? > I would actually like to know how does one get to this link > <https://chromestatus.com/feature/5110990717321216/gate/5269432429969408/intent> > you > have sent for a feature, as at least as a feature owner for Incoming Calls > notifications chromestatus does not provide any indication on where to > generate or find the current template for the blink-dev email to go to OT. > > Could I be missing permissions to see this? > The UI is a bit non-obvious. Click "API owners", and then a "Draft Intent to Experiment email" button will appear on the right-hand side. The idea is that it's the same as the other approval processes (Privacy, WP Security, Debuggability). > > > > > > *Regards,* > > *Diego González* > (PWA PM @ Edge) > > > > ------------------------------ > *From:* Domenic Denicola <dome...@chromium.org> > *Sent:* 01 July 2025 04:52 > *To:* Diego Gonzalez <luigo...@microsoft.com> > *Cc:* blink-dev <blink-dev@chromium.org>; Stanley Hon < > sta...@microsoft.com>; Rob Paveza <rob.pav...@microsoft.com>; Limin Zhu > (Edge) <li...@microsoft.com>; Ajay Rahatekar <ajayrahate...@google.com> > *Subject:* [EXTERNAL] Re: [blink-dev] Intent to [Experiment] Origin > Trial: Incoming Call Notifications > > You don't often get email from dome...@chromium.org. Learn why this is > important <https://aka.ms/LearnAboutSenderIdentification> > I'm curious how this email was generated. It doesn't follow the template > created > from ChromeStatus > <https://chromestatus.com/feature/5110990717321216/gate/5269432429969408/intent>, > and the non-standard subject line meant it wasn't picked up by the API > owners review dashboard. > > Anyway, this LGTM, and is approved to experiment from M139 to M141. > However, please respond to the following, and correct the ChromeStatus > entry as appropriate: > > - The ChromeStatus entry says TAG review is not applicable. (The above > email is missing this field.) Can you explain why that would be? > - The ChromeStatus entry says there is no interop and compat risk. > This seems unlikely, especially given that there are no signals from other > vendors? > - The ChromeStatus entry says there is no Finch flag. A Finch flag is > required for all new features. Perhaps you confused Finch flag and Flag > name on about://flags? > - The ChromeStatus entry has no OT milestones, but this email has > them. Please be sure to enter those into ChromeStatus so that it is > properly tracked. > - This email contains different answers for debuggability, platform > support, and summary versus ChromeStatus. Please ensure these get > harmonized. > > > On Tue, Jun 17, 2025 at 5:55 AM 'Diego Gonzalez' via blink-dev < > blink-dev@chromium.org> wrote: > > *Spec* > The shape of the API and discussions are based on *this explainer > <https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Notifications/notifications_actions_customization.md>*. > Intended to live in the *Notifications API > <https://notifications.spec.whatwg.org/>* spec. > > *Summary* > We would like to propose an extension to the *Notifications API > <https://notifications.spec.whatwg.org/>* standard for incoming call > scenarios to allow the notification action buttons to be customized and > also allow the application to play a ringtone. This capability would make > the incoming call notifications, which may require a faster immediate > response, clearly distinguishable from the others to the user and would > also contribute to increasing accessibility on the Web. > > *Link to “Intent to Prototype” blink-dev discussion* > *Intent to Prototype > <https://groups.google.com/a/chromium.org/g/blink-dev/c/PtHemJah2Qc/m/gsrgJW9LCAAJ>* > > *Goals for experimentation* > Get developer feedback on the effectiveness of the API. Looking for > information regarding developer ergonomics, action button scenarios and > general overall usage. > > *Experimental timeline* > Next availability -> Start M139 until M141 > > *Any risks when the experiment finishes?* > If there is no `incoming-call` notification scenario, the notification may > fallback to `default` and lose its potential “priority” status that could > position it above other notifications. The notifications would lose their > ringtone as well. > > *Reason this experiment is being extended* > First time OT, this is not and extension. > > *Ongoing technical constraints* > None > > *Debuggability* > As this is an extension to an existing API, there is no expected change in > debugging behaviours. > > *Will this feature be supported on all five Blink platforms supported by > Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?* > This OT will be Windows only. > No mobile, no macOS/Linux/CrOS. These will be re-evaluated after the OT. > > *Link to entry on the feature dashboard* > *https://chromestatus.com/feature/5110990717321216 > <https://chromestatus.com/feature/5110990717321216>* > > > > *Diego González* > Senior Product Manager > *Microsoft Edge* > > -- > 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+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DU4PR83MB077216A4DFAA844FC382E5BECC70A%40DU4PR83MB0772.EURPRD83.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DU4PR83MB077216A4DFAA844FC382E5BECC70A%40DU4PR83MB0772.EURPRD83.prod.outlook.com?utm_medium=email&utm_source=footer> > . > > -- 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+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra9F56ir7uxGcAuQBYfU4J1pYyivNA_Y3cqc0kQ65y4OuA%40mail.gmail.com.
