-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Race between showNotification & getNotifications #90
Comments
That sounds reasonable. I'm not even sure why we resolve early. @beverloo? |
We actually implement that part of the spec incorrectly then - Chrome resolves once the notification has been shown. This really helps in avoiding internal logic for keeping things around until the notification is ready, e.g. after a Waiting LGTM. |
jakearchibald
added a commit
to jakearchibald/notifications-1
that referenced
this issue
Jan 12, 2017
jakearchibald
added a commit
to jakearchibald/notifications-1
that referenced
this issue
Jan 12, 2017
jakearchibald
added a commit
to jakearchibald/notifications-1
that referenced
this issue
Jan 13, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the current spec, it seems likely that the notification shown by
showNotification
won't be in the sequence returned bygetNotifications
.showNotification
resolves before fetching icons & running display steps, and the notification isn't added to the list of notifications until after the display steps.Possible solutions:
showNotification
should resolve later, once the notification is shown. Or, the notification should be added to the list of notifications sooner. Or,getNotifications
should wait for pending notifications.The first solution feels simplest.
The text was updated successfully, but these errors were encountered: