disable confirmed delivery for Safari

This feature causes iOS push endpoint to become invalid due Apple's
restriction on background execution. We are disabling Safari even
for macOS to be safe as Apple could enforce this there too at any
time.

Author: jkasten2

src/service-worker/ServiceWorker.ts

@@ -345,6 +345,9 @@ export class ServiceWorker {
     if (!notification)
       return null;
 
+    if (!ServiceWorker.browserSupportsConfirmedDelivery())
+      return null;
+
     // Received receipts enabled?
     if (notification.rr !== "y")
       return null;
@@ -375,6 +378,19 @@ export class ServiceWorker {
     return await OneSignalApiBase.put(`notifications/${notification.id}/report_received`, postData);
   }
 
+  /**
+   * Confirmed Delivery isn't supported on Safari since they are very strict about the amount
+   * of time you have to finish the onpush event. Spending to much time in the onpush event
+   * will cause the push endpoint to become revoked!, causing the device to stop receiving pushes!
+   *
+   * iPadOS 16.4 it was observed to be only about 10 secounds.
+   * macOS 13.3 didn't seem to have this restriction when testing up to a 25 secound delay, however
+   * to be safe we are disabling it for all Safari browsers.
+  */
+  static browserSupportsConfirmedDelivery(): boolean {
+    return !bowser.safari
+  }
+
   /**
    * Gets an array of active window clients along with whether each window client is the HTTP site's iFrame or an
    * HTTPS site page.