W3C

APA Push/Notifications coord

11 Oct 2017

Agenda

See also: IRC log

Attendees

Present
Anne, Chaals, Janina, Léonie, MichaelC, Peter_Beverloo
Regrets
Chair
Janina
Scribe
tink

Contents


<scribe> scribe: tink

<annevk> chaals: https://lists.w3.org/Archives/Public/public-apa/2017Oct/0017.html

Topic Overview & Brief Participant Intros

Push/Notification RFE Discussion

JS: A requested enhancement, originally filed against Push API.
... Then at the suggestion of the editors and WebPlat chairs was filed against Notifications API.

<MichaelC> Comment filed on Push API

<MichaelC> Comment filed on Web Notifications

JS: Web Payments IG is also interested in the enhancement request.
... The ability to put notifications into "Do Not Disturb (DND(" mode.
... to temporarily put a hold on notifications, so they don't interupt an ongoing/current activity like completing a payment.
... or to stop notifications for accessibility reasons.

AVK: This clarifies a lot for me.
... I tend to think of APIs as a backend/development thing.
... Rather than in terms of the UA/AT.
... The thing to note in the spec is an accessibility consideration.

LW: Are you thinking this is for the Notifications spec or the Push spec now?

AVK: The Push spec is not about displaying anything to the user.

PB: Agree.
... This is better suited to the Notifications spec.

AVK: We can have language there around UA/AT.
... To provide guidance based on the use cases provided.

CMN: Firefox and Yandex both have mechanisms for turning off notifications for specified periods of time.
... Providing spec guidance to recommend this sort of behaviour seems achievable.

PB: It would be easy for us to implement something like this in Chrome too.
... But the browser doesn't always have control over all notifications.

LW: Yes, for complete DND it would need to be handled at the OS level.

CMN: It depends.
... The browser is often the key UA.
... So being able to set this in the browser isn't the complete solution, but it will cover many scenarios.

PB: Do you have an idea of notifications shown on any platform that come from the browser as opposed to other UA?

CMN: Too many variables to know.
... In my world it's a high proportion of webapps because I kill off other things fairly ruthlessly.

AVK: Think it would be useful to note something in the spec.

Next Steps

<chaals> [In fullscreen is another time when notifications *may* not be welcome.]

LW: Something like the security/privacy considerations we typically include.

PB: As it's own section?

LW: Yes, but in the same place in the spec where we include other considerations like sec/priv.

CMN: Agree with Léonie.
... It's editorial though.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/10/11 17:27:54 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Present: Anne Chaals Janina Léonie MichaelC Peter_Beverloo
Found Scribe: tink
Inferring ScribeNick: tink
Agenda: https://lists.w3.org/Archives/Public/public-apa/2017Oct/0017.html
Got date from IRC log name: 11 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/11-apa2-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]