diff options
| author | bemasc@chromium.org <bemasc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-22 01:21:46 +0000 |
|---|---|---|
| committer | bemasc@chromium.org <bemasc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-22 01:21:46 +0000 |
| commit | 31268815420a038ad43ba7808862f97a8a129801 (patch) | |
| tree | 88e626cda633e1a204db2dff15f14b74a4617baa /content/renderer/dom_serializer_browsertest.cc | |
| parent | 7be9c7dd3ddd242578bae0a07d4c758c23843017 (diff) | |
| download | chromium_src-31268815420a038ad43ba7808862f97a8a129801.zip chromium_src-31268815420a038ad43ba7808862f97a8a129801.tar.gz chromium_src-31268815420a038ad43ba7808862f97a8a129801.tar.bz2 | |
Currently, Chromium does not listen for error notifications from QTKit, i.e. they are ignored. QTKit device creation can succeed, and then later fail asynchronously via such a message, never producing any frames. If Chromium doesn't listen for the error notifications, then this results in a getUserMedia call that never fires its success or failure callbacks.
For example, with this change, if too many cameras are connected to the same USB hub, then bandwidth limitations may cause some of the cameras to fail to open. This results in a QTCaptureSessionRuntimeErrorNotification whose localized text reads "The operation couldn't be completed. (OSStatus error -536870164.)". With this change, that notification results in a getUserMedia failure callback to the javascript (with event.name == 'PERMISSION_DENIED', which is the only currently supported error code).
BUG=265704
Review URL: https://chromiumcodereview.appspot.com/22982008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218892 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/dom_serializer_browsertest.cc')
0 files changed, 0 insertions, 0 deletions