Based on the results for both Chrome + Safari for the Throws if the promise [[state]] is not 'created'. sub-test, I suspect that neither follow the spec in checking user activation before step 7 (If request.[[state]] is not "created").

At least for Chrome, reading our code, we do the first set of checks in this order I believe:

• 5. If document is not fully active, then return a promise rejected with an "AbortError" DOMException.
• 7. If request.[[state]] is not "created" then return a promise rejected with an "InvalidStateError" DOMException.
• 2. If the relevant global object of request does not have transient activation, return a promise rejected with with a "NotAllowedError" DOMException.

I can't quite find if or when we do the check in step 6 yet :D. (It is optional).