This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 30176 - Specify how the Speech Recognition API (doesn't) work on non-secure contexts
Summary: Specify how the Speech Recognition API (doesn't) work on non-secure contexts
Status: RESOLVED MOVED
Alias: None
Product: Speech API
Classification: Unclassified
Component: Speech API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Glen Shires
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-04 15:54 UTC by Philip Jägenstedt
Modified: 2018-08-06 10:54 UTC (History)
1 user (show)

See Also:

Attachments

Description Philip Jägenstedt 2017-09-04 15:54:32 UTC 

    


    


      



        
          Comment 1
        

        
          Philip Jägenstedt

        

        
        

        
          2017-09-04 15:59:48 UTC
        

      






https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html should limit the speech recognition API to secure contexts <https://w3c.github.io/webappsec-secure-contexts/> since it requires the use of a microphone, and getUserMedia() has a note about this:
https://w3c.github.io/mediacapture-main/#local-content

In Chrome, getUserMedia() throws/rejects on non-secure contexts.

For speech, this could be done either by throwing an exception, or using [SecureContext] in IDL.

Context: a change to this is being made in https://groups.google.com/a/chromium.org/d/msg/blink-dev/PdGY39MAaeM/LTaCl_f4AQAJ

    


    


      



        
          Comment 2
        

        
          Philip Jägenstedt

        

        
        

        
          2018-08-06 10:54:38 UTC
        

      






Sent a PR: https://github.com/w3c/speech-api/pull/31