As a developer implementing push notifications for mobile web browsers I would like to be able to specify when a notification should chime or vibrate the phone such that I can get the attention of my users when it is important.
On Fx Android 1. goto: https://people.mozilla.org/~mnoorenberghe/w3c_notifications.htm or https://people.mozilla.org/~ewong2/push-notification-test/ 2. trigger a web notification or push notification actual: no chime or vibrate upon receiving notification expected: phone should chime and vibrate. Chrome does this for push notifications (don't seem to support web notifications on android)
This doesn't seem to be a regression, but with the increase use of push notification rolling out in nightly, we should consider supporting this.
Does the spec give websites the ability to choose a noise level, the way native app developers have the ability to do that? This seems like it has the potential to be really obnoxious. NI to Barbara to get this on her radar.
"When updating a notification, sites can specify whether the device should alert the user with sound or vibration, or remain silent." http://blog.chromium.org/2016/03/chrome-50-beta-push-notification.html
What do we have to do in order to make this work, as Edwin mentioned Chrome on Android doesn't support it either? Does it for iOS? Trying to understand what piece of browser piece needs to support this?
Flags: needinfo?(bbermes) → needinfo?(edwong)
:barbara - I meant Chrome DOES support vibration/chime for push notifications but for general web notifications (without push from 2-3yrs ago)they've dropped support altogether
bryan - we should be explicit about how we want to support this in Fx48, which will be our first android release with push notifications
Just so we're clear on the state of push and (interrupting) notifications. Chrome on Android supports this spec. Chrome on iOS? (unclear) I've added the user story to this bug. We're requesting that Android support ringing or vibrating the device as specified by the push notification. This change will keep us compatible with Chrome on Android and give developers the right level of control to make different types of push notifications relevant as needed. We need to investigate iOS support, if Chrome doesn't yet support this on iOS it can be an advantage for us and if they already to then we'll need to add it to remain compatible across mobile operating systems. @barbara, This is an important part of push support for mobile to remain compatible with modern mobile browsers. I'd like to get this in the backlog and see if Fx48 is possible.
User Story: (updated)
Flags: needinfo?(bclark) → needinfo?(bbermes)
Web Notifications spec: https://notifications.spec.whatwg.org/
(In reply to Barbara Bermes [:barbara] from comment #9) > margaret, I assume this requires frontend UI work, is this something we > could squeeze in after all the mobile focus updates? > > If not, is another team able to work on this instead? > > While I agree we should stay competitive, I wonder if this is really that > urgent at this point, due to all the re-org? This is a web API, so this is platform work. There is no UI. Yes, you'll need to use Android APIs, but platform people can do that. jchen or someone on the DOM team should be able to implement this.
margaret, I assume this requires frontend UI work, is this something we could squeeze in after all the mobile focus updates? If not, is another team able to work on this instead? While I agree we should stay competitive, I wonder if this is really that urgent at this point, due to all the re-org?
Consider whether 1236902 is a dup of this (or vice versa)?
> I wonder if this is really that urgent at this point, due to all the re-org? Without this, FF on Android is a non-starter for *any* real time messaging or apps w. state updates. Chrome only supports the Notification API on Service Workers, which I've just added to my own messaging so I can get full support on Android: https://github.com/vandys/-webXMPP People are not going to be OK with turning on their phone every other minute. Please, please fix this. Thanks.
I really need this. Right now notifications are almost useless.
This could be fixed quite simple in: https://hg.mozilla.org/mozilla-central/file/tip/mobile/android/base/java/org/mozilla/gecko/notifications/NotificationClient.java#l149 Add the following : > .setDefaults(DEFAULT_ALL)  https://developer.android.google.cn/reference/android/support/v4/app/NotificationCompat.Builder.html#setDefaults(int) Additional notification options also could be supported easily, like re-notify, custom vibration patterns, etc.
Joe, this might be something we can put on the Trello board for Fennec....
Flags: needinfo?(bbermes) → needinfo?(jcheng)
In an other bug the default sound for notifications has been enabled, but vibration is still missing. It would be great if you could add this too.
Enabling sound was great, please set the bit for blinking the notification LED as well. Otherwise if you miss the sound you won't know about messages waiting until you turn on the screen.
IS this going to get fixed?
My "daily driver" is Android with Fennec, using long polling and HTML5 Notifications for email/SMS/XMPP/telemtry. Your adding of sound for notifications was great; I can provide a user story if that can help you think about vibration and LED as well.
Currently not scheduled, will updated once priorities change.
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.