Notifications aren't invoked again if their scheduledTime elapsed while Clippings not in use

[aecreations]

Clippings 7.0rc4

While testing backup reminder notifications, it was discovered that if Clippings was not in use (e.g. because the computer was asleep) at the time it was supposed to be invoked (represented by the scheduledTime property on the alarm that calls the background script function to perform notification processing), the alarm is never invoked again, causing the notification to be suppressed.

Note that this situation is different from when the background script is terminated. In this case, the background script is restarted when the alarm is invoked.

Is this a bug with the Alarms API when used in a non-persistent MV3 background script?

[aecreations]

This should be fixed for backup reminders and Sync Clippings Helper update notifications.

The post-upgrade notifications are lower priority, since their appearance is intended to be less frequent (once a day, maximum 2 invocations).

[aecreations]

I ran a test using a test extension that fires an alarm every 5 minutes. Even if the computer was suspended when the alarm is due to fire, the alarm continues to fire at 5 minute intervals once the computer was resumed. This was tested on Firefox 115 ESR, 132 and 133.

The issue likely is in the code that calculates whether or not to show the backup notification based on the last backup reminder date.