[w3c/manifest] BeforeInstallPromptEvent: Should prompt throw InvalidStateError if preventDefault not called? (#577)

A [previous draft of the spec](https://github.com/w3c/manifest/pull/506/files) included this language in the `prompt` method:

> If the *canceled* flag is unset, throw an `InvalidStateError`, optionally with the message informing the developer that `.prompt()` needs to be called after `.preventDefault()`.

This text didn't make it into the final version -- I actually didn't notice it disappearing. Was it intentional?

Chrome's implementation does currently throw `InvalidStateError` in this case. However, on reflection, especially if #576 is actioned, it doesn't make sense to throw an error if `preventDefault` is not called (since the default behaviour may in fact not be to show a prompt, and therefore it's sensible to call `prompt` without `preventDefault`). In that case, this is a WontFix.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/577