Dismissed notifications with same tag won't trigger onclick handler for next notification

[r0stig]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success. (Similar to this issue but that issue is closed: Notifications that shares the same tag won't trigger onclick on every second notification #17706)

Issue Details

• Electron Version:
  • 10.1.2
• Operating System:
  • Mac OS 10.15.6
• Last Known Working Electron version:
  • I think this PR is the cause of this bug: fix: remove same-tag notifications before showing new ones #24302

Expected Behavior

The onclick-handler for a notification in the renderer process should always be fired upon click when the notification object shares the same tag.

Actual Behavior

Only every second notification click fires the onclick handler when the notifications share the same tag when the notification before is dismissed manually or automatically.

To Reproduce

https://github.com/r0stig/electron-quick-start

$ git clone git@github.com:r0stig/electron-quick-start.git
$ npm install
$ npm start

• Click on the button "send notification"
• Wait for the notification to be closed automatically or dismiss manually
• Click on the button "send notification"
• Click on the notification and notice that the onclick-handler did not fire

Screenshots

See clip:

Additional Information

This bug is similar to this closed issue a while ago: #17706

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[github-actions]

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.