-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Constructors for speech events #14
Comments
Yes, it should have a constructor, also raised by @smaug---- before in https://www.w3.org/Bugs/Public/show_bug.cgi?id=28867. Change should be trivial, but I'm currently converting the spec to Bikeshed, so best to do it after that. |
When sending #45 I didn't read the issue description to spot that Edge and Firefox already disagree about whether the argument should be required. In this case, I would like to align with Firefox, because otherwise the |
Interop is good, but what's the use case for constructing one of these? I suppose it's potentially useful for writing unit tests, but I can't think of anything else. |
Testing, and consistency with other events. |
Currently
new SpeechSynthesisEvent("pending", { utterance: new SpeechSynthesisUtterance() })
works on Edge and Firefox but throws on Chrome.Edge: only requires the first argument
Firefox: requires both the first and second arguments
Chrome: always throws
Can we spec this to align browser behaviors?
The text was updated successfully, but these errors were encountered: