A number of users are running in to Web Notification database read errors when handling an activation. This results in a user experience where nothing happens, which is not ideal.

For the immediate issue, we could either close the affected notification or open a tab for their origin. I'm erring towards the former.

For the longer-term solution, we need to figure out why there are orphaned notifications in the OS' notification center. My gut feel is that part of this will be caused by things like dropped Service Workers. We can issue Close() calls when the associated data is being removed in such cases.