Closed
Bug 1051130
Opened 10 years ago
Closed 9 years ago
Make SpeechGrammarList's addFromURI/addFromString async with Promise
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: anatal, Unassigned)
References
Details
(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
Reporter | ||
Comment 1•10 years ago
|
||
There is a bug at W3C Bugzilla requesting to Fix the draft here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26520
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
Reporter | ||
Comment 2•10 years ago
|
||
Should we move forward with this even while W3C does not reply or is better wait ?
Flags: needinfo?(ggoncalves)
Flags: needinfo?(bugs)
Reporter | ||
Updated•10 years ago
|
Comment 3•10 years ago
|
||
AFAIK no one else implements those methods anyway, and adding return value
shouldn't break existing code anyway.
Flags: needinfo?(bugs)
Updated•10 years ago
|
Flags: needinfo?(ggoncalves)
Reporter | ||
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
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.
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26520
Comment 5•9 years ago
|
||
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?
Comment 7•9 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•