Closed marcoscaceres closed 2 years ago
Our implementation runs one of the steps out of order: the userVisibleOnly requirement is only checked quite a late in the process, as there may be (toady hypothetical) cases in which we don't require it, e.g. for extensions.
Ok, I'll move that to async part and just add a note. The ordering when that happens doesn't matter too much.
The following are not testable/observable, but spec bugs nonetheless:
PushSubscriptionOptionsInit
usage.userVisibleOnly
member.Preview | Diff