Do not hash default and communications media device ID

content/browser/renderer_host/media/audio_renderer_host.cc

Index: content/browser/renderer_host/media/audio_renderer_host.cc
diff --git a/content/browser/renderer_host/media/audio_renderer_host.cc b/content/browser/renderer_host/media/audio_renderer_host.cc
index 8196c8701c403d6c26f2bda9b08998b8d833e630..1b72daa1cb654477ad0b2089c579dcde0b52c4ce 100644
--- a/content/browser/renderer_host/media/audio_renderer_host.cc
+++ b/content/browser/renderer_host/media/audio_renderer_host.cc
@@ -82,8 +82,11 @@ GURL ConvertToGURL(const url::Origin& origin) {
 bool IsValidDeviceId(const std::string& device_id) {
   static const std::string::size_type kValidLength = 64;
 
-  if (device_id.empty())
+  if (device_id.empty() ||
+      device_id == media::AudioManagerBase::kDefaultDeviceId ||
+      device_id == media::AudioManagerBase::kCommunicationsDeviceId) {

[ajm, 2015/09/28 22:47:18]

Does it matter that ChromeOS is not using these IDs when a mic array is
available? See line 42-43:
https://codereview.chromium.org/1362093002/diff/140001/media/audio/cras/audio...

[Guido Urdaneta, 2015/09/29 10:36:12]

No, it does not matter. This is a check for hashed device IDs coming from the
renderer.
Those special IDs in ChromeOS will come hashed as an hex string from the
renderer just like nondefault IDs.

[tommi (sloooow) - chröme, 2015/09/29 11:59:51]

Is it using any other "known-and-not-translated" ID?
If it's only using hashed IDs, then I don't think it makes a difference.

[ajm, 2015/09/29 16:00:55]

Great, thanks.

[ajm, 2015/09/29 16:00:55]

No.

     return true;
+  }
 
   if (device_id.length() != kValidLength)
     return false;