Bug 180699

Summary: getUserMedia is resolving before the document knows it is capturing
Product: WebKit Reporter: youenn fablet <youennf>
Component: WebRTCAssignee: youenn fablet <youennf>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, eric.carlson, jer.noble, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch
none
Rebasing
none
Patch for landing none

youenn fablet
Reported 2017-12-12 09:13:27 PST
Sometimes getUserMedia promise will be resolved and autoplay will not be disabled as the promise resolves before the stream is producing data and the document knows it is capturing. We may want to delay promise resolution until the stream is ready to produce data.
Attachments
Patch (9.73 KB, patch)
2017-12-12 10:09 PST, youenn fablet
no flags
Patch (21.88 KB, patch)
2017-12-12 11:19 PST, youenn fablet
no flags
Rebasing (16.16 KB, patch)
2017-12-12 13:38 PST, youenn fablet
no flags
Patch for landing (16.16 KB, patch)
2017-12-12 15:17 PST, youenn fablet
no flags
youenn fablet
Comment 1 2017-12-12 10:09:51 PST
youenn fablet
Comment 2 2017-12-12 11:19:12 PST
youenn fablet
Comment 3 2017-12-12 13:38:35 PST
Created attachment 329148 [details] Rebasing
Eric Carlson
Comment 4 2017-12-12 15:12:46 PST
Comment on attachment 329148 [details] Rebasing View in context: https://bugs.webkit.org/attachment.cgi?id=329148&action=review > Source/WebCore/Modules/mediastream/UserMediaRequest.cpp:260 > + { Nit: indentation.
youenn fablet
Comment 5 2017-12-12 15:17:33 PST
Created attachment 329166 [details] Patch for landing
WebKit Commit Bot
Comment 6 2017-12-12 17:39:39 PST
Comment on attachment 329166 [details] Patch for landing Clearing flags on attachment: 329166 Committed r225828: <https://trac.webkit.org/changeset/225828>
WebKit Commit Bot
Comment 7 2017-12-12 17:39:41 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 8 2017-12-12 17:40:32 PST
Note You need to log in before you can comment on or make changes to this bug.