Re: [w3c/push-api] Drop permissionState()'s argument? (Issue #417)

annevk left a comment (w3c/push-api#417)

I see, but any conforming implementation is required to ignore the argument (except for IDL purposes) as things stand today specification-wise.

But it's clear Chromium is doing something else:
```
  // The `userVisibleOnly` flag on |options| must be set, as it's intended to be
  // a contract with the developer that they will show a notification upon
  // receiving a push message. Permission is denied without this setting.
  //
  // TODO(peter): Would it be better to resolve DENIED rather than rejecting?
  if (!options->hasUserVisibleOnly() || !options->userVisibleOnly()) {
    resolver->Reject(MakeGarbageCollected<DOMException>(
        DOMExceptionCode::kNotSupportedError, kUserVisibleOnlyRequired));
    return promise;
  }
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/417#issuecomment-3597791054
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/417/3597791054@github.com>