Re: [w3ctag/design-reviews] Launch Events (#372)

So I'm a little nervous about this bit:



> If the launch handler does not:
> 
> i.   Focus a client.
> ii.   Open a new client.
> iii.   Show a notification (Note: permission to show notifications is required).
> 
> then the user agent should assume that the launch handler did not handle the launch, and should continue as if there were no launch event handler.

makes me a little bit nervous.  I think in other event-based APIs things like this have tended to be handed more explicitly, i.e., with `event.preventDefault()` if you want to suppress the default action.  Though maybe that's not the convention for service workers.  (Is this at all related to `ExtentableEvent`?)

On the other hand, I suppose this behavior makes sense here, since it's both bad for these sorts of things to disappear without an action, and also bad for them to result in two actions.

(Also, is it related to the bit about the `[handlePending]` slot, which I can't seem to find referenced somewhere else?)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/372#issuecomment-561382115