Closed Bug 1051130 Opened 6 years ago Closed 5 years ago

Make SpeechGrammarList's addFromURI/addFromString async with Promise


(Core :: DOM: Core & HTML, defect)

Not set





(Reporter: anatal, Unassigned)


(Blocks 1 open bug)


(Whiteboard: [webspeechapi])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140716183446
There is a bug at W3C Bugzilla requesting to Fix the draft here:

We need to modify our implementation of SpeechGrammarList to work async with Promise
OS: Mac OS X → All
Hardware: x86 → All
Summary: Make SpeechGrammarList's addFromURI/addFromString async → Make SpeechGrammarList's addFromURI/addFromString async with Promise
Should we move forward with this even while W3C does not reply or is better wait ?
Flags: needinfo?(ggoncalves)
Flags: needinfo?(bugs)
Blocks: 1049931
Blocks: 1051148
No longer blocks: 1049931
AFAIK no one else implements those methods anyway, and adding return value
shouldn't break existing code anyway.
Flags: needinfo?(bugs)
Flags: needinfo?(ggoncalves)
Blocks: 1067689
No longer blocks: 1051148
Ever confirmed: true
Whiteboard: [webspeechapi]
I'd prefer to stick with the spec until W3C responds to our bug[1]. In the mean time the methods
can simply be synchronous.

Well, we can't load synchronously from network.
(sync IO is not acceptable on main thread)
I'll assume for the moment that "sync IO is not acceptable on main thread".

Must addFromURI and addFromString be called from the main thread? What of,
for example, web workers?
Well, we don't have any speech API stuff on workers. But yes, there sync operations would be ok.
In light of the movement of the grammar check to start() in Bug 1185018
this bug is invalid.
Closed: 5 years ago
Resolution: --- → INVALID
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.