UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Call chrome.notifications.create() with progress at 0
2. Immediately call chrome.notifications.update() with progress at > 0
3. Chrome returns wasUpdated = true while it has not been updated

What is the expected behavior?
The notification should update or return wasUpdated = false.

What went wrong?
We noticed an issue with notifications triggered by our app: the progress notifications stay at 0% and never get cleared even if we do call chrome.notifications.clear() with the correct notification ID.

I believe the issue is related to the notification not being initialized when doing the first update call. The current workaround to the problem I found is to make sure not to call chrome.notifications.update() before 500ms after creating the notification.

Please note that we did not have this problem before with the non-native OSX notifications.

Did this work before? Yes 58.x.x.x

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: OS X 10.12.5
Flash Version: