Closed Bug 1244102 Opened 8 years ago Closed 8 years ago

Notifications disappear during interaction

Categories

(Toolkit Graveyard :: Notifications and Alerts, defect)

defect
Not set
normal

Tracking

(firefox47 affected)

RESOLVED WONTFIX
Tracking Status
firefox47 --- affected

People

(Reporter: callahad, Unassigned)

References

Details

(Keywords: DevAdvocacy)

Notifications dismiss themselves, even when the user is interacting with the notification.



Steps to Reproduce:

1. Trigger a notification, e.g., by using the demo at https://davidwalsh.name/demo/notifications-api.php

2. Click the '...' (OS X) or gear icon (Windows) to reveal extended actions like "Disable notifications from davidwalsh.name" and "Notification Settings"

3. Hover over these options, and wait five seconds.



What happens:

1. The notification times out and dismisses itself, even in the midst of user interaction.



What should happen:

1. The notification should persist while the user is interacting with it.
Thanks, Dan! Unfortunately, there isn't much we can do about the OS X behavior. I suspect it's because we're using a private API to add the action menu, and it doesn't anticipate being used with a banner notification. iCal has a similar menu for reminders, but its alerts remain visible until you click "Snooze." Windows shouldn't be affected, since it uses a different notification backend.

We could use the same backend on all our platforms, as Chrome does. There's some discussion about that in bug 1148410, and we can use this ticket as another reason to go with that approach.

I still think the native platform integration is a win (it's consistent with other apps, and uses the same notification center), though it leads to UX paper cuts like this. We could also make notifications persistent by default, though that can be a poor experience if you receive too many of them.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
See Also: → 1148410
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.