diff --git a/notifications.bs b/notifications.bs index 711d3ff..baa493d 100644 --- a/notifications.bs +++ b/notifications.bs @@ -522,13 +522,8 @@ specified) run these steps:
  • If one of notification's actions was activated by the user, then set action to that action's name. -

  • Let callback be an algorithm that when invoked with a global, - fires a service worker notification event - named notificationclick given notification and action on - global. - -

  • Then run Handle Functional Event with notification's - service worker registration and callback. +

  • Fire a service worker notification event named "notificationclick" given + notification and action.
  • @@ -571,18 +566,9 @@ must be run.

    To handle close events given a notification, run these steps:

      -
    1. -

      If notification is a persistent notification and - notification was closed by the user, then: - -

        -
      1. Let callback be an algorithm that when invoked with a global, - fires a service worker notification event - named notificationclose given notification on global. - -

      2. Then run Handle Functional Event with notification's - service worker registration and callback. -

      +
    2. If notification is a persistent notification and notification + was closed by the user, then fire a service worker notification event named + "notificationclose" given notification.

    3. If notification is a non-persistent notification, then queue a task to fire an event named close on the {{Notification}} object representing @@ -1083,13 +1069,18 @@ the same underlying notification of {{Notification}} objects already in e


      -

      To fire a service worker notification event named e -given notification and action, -fire an event named e, using {{NotificationEvent}}, with the -{{NotificationEvent/notification}} attribute initialized to a new -{{Notification}} object representing notification and the -{{NotificationEvent/action}} attribute initialized to action. - +

      To fire a service worker notification event named name given +notification (a notification), and an optional action (a DOMString, +defaulting to the empty string), Fire Functional Event name using +{{NotificationEvent}} on notification's +service worker registration with the following properties: + +

      +
      {{NotificationEvent/notification}} +
      A new {{Notification}} object representing notification. +
      {{NotificationEvent/action}} +
      action +

      The {{NotificationEvent/notification}} attribute's getter must return the value it was initialized to. @@ -1165,8 +1156,6 @@ by John Gregg (Google, urlPrefix: https://html.spec.whatwg.org/multipage/ urlPrefix: webappapis.html; type: dfn text: entry settings object -urlPrefix: https://w3c.github.io/ServiceWorker/; type: dfn - text: handle functional event; url:handle-functional-event-algorithm urlPrefix: https://w3c.github.io/vibration/ urlPrefix: #dfn-; type: dfn text: perform vibration