User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20151216175450 Steps to reproduce: Note: The below steps include an example test case (in this case, a demo from the Mozilla Demo Studio), but is NOT unique to the test case and can be reproduced on any site that implements HTML5 notifications in a similar manner. 1. Navigated to a Mozilla Demo Studio demo for HTML5 notifications (https://developer.mozilla.org/ms/demos/detail/html5-notifications) in Firefox for Android on a LG Nexus 5 on stock Android 5.1.1. 2. Launched the demo web app. 3. Entered a title and message and 0 second time delay, then clicked the "Display Notification" button. 4. When prompted by Firefox, "Allowed" the page permission to push notifications to my device. 5. Entered a new title and message and additionally a 5 second time delay, then clicked the "Display Notification" button. 6. Turned off the screen of my Nexus 5 device and awaited for the notification from the web app. Actual results: Firefox sent a push notification to the device, but offered no indication that it had done so. There was neither an audio cue (e.g: message beep) nor a visual cue (e.g: notification indicator light) that the push notification had been sent to the device. Expected results: Ideally, push notifications triggered by HTML5 notifications should either trigger the device's notification light to alert users to their notifications, or (better yet) be completely configurable so users can choose whether or not the push notifications come with a notification light, audio cue (e.g: message beep), etc.

Hello, I have tested this issue on a Nexus 9 (Android 7.0) device and the issue is indeed reproducible no visual, audio or tactile responses are received by the device when the screen is turned off. Notes: - There is only a visual notification in the Notification Bar when the screen is turned on.

I can confirm this on vanilla AOSP Android Marshmallow with 50.1.0, with my own messaging app. Notifications which can only be detected by remembering to bring the phone up to your face, turning on the screen, and seeing if a notification is displayed? That more or less defeats the purpose of notifications! If you don't want to enable it by default like you did for Firefox OS, please at least give an option in the notification permission popup.

Mass wontfix for bugs affecting firefox 52.

Android O means that we could make this user configurable very easily without having to - write our own configuration UI, and - implementing our own system of setting the notification priority based on the user's settings. So should we a) create a notification channel for HTML5 web site notifications (it seems that notification channels just keep on multiplying)? b) with what name ("Site notifications"?)? c) which default priority [1] - maybe IMPORTANCE_DEFAULT, i.e. audible but not heads-up, plus additionally the notification light? Additionally, should we also change the notification priority for Android versions prior to Oreo - bearing of course in mind that whatever we choose as the default there *won'*t be user configurable? [1] https://developer.android.com/training/notify-user/channels#importance

Moving NI back over to bug 1493864. As for this bug, if we don't want to do anything further about pre-Android O, we can just close this (or mark *this* bug as a duplicate of bug 1493864) then. Also to note that at least sound was added in bug 1378445.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.