Add audible, muted to Tab, c.t.query, c.t.update, and c.t.onUpdated where relevant

chrome/browser/extensions/api/tabs/tabs_api.cc

Index: chrome/browser/extensions/api/tabs/tabs_api.cc
diff --git a/chrome/browser/extensions/api/tabs/tabs_api.cc b/chrome/browser/extensions/api/tabs/tabs_api.cc
index 4816da7e0687d8ce20a9b3f0af4717c47edc2252..c157b3cad2cd007e5e8f5bed0705870c410c906a 100644
--- a/chrome/browser/extensions/api/tabs/tabs_api.cc
+++ b/chrome/browser/extensions/api/tabs/tabs_api.cc
@@ -43,6 +43,7 @@
 #include "chrome/browser/ui/host_desktop.h"
 #include "chrome/browser/ui/panels/panel_manager.h"
 #include "chrome/browser/ui/tabs/tab_strip_model.h"
+#include "chrome/browser/ui/tabs/tab_utils.h"
 #include "chrome/browser/ui/window_sizer/window_sizer.h"
 #include "chrome/browser/web_applications/web_app.h"
 #include "chrome/common/chrome_switches.h"
@@ -908,6 +909,16 @@ bool TabsQueryFunction::RunSync() {
         continue;
       }
 
+      if (!MatchesBool(params->query_info.audible.get(),
+                       chrome::IsPlayingAudio(web_contents))) {
+        continue;
+      }
+
+      if (!MatchesBool(params->query_info.muted.get(),
+                       chrome::IsTabAudioMuted(web_contents))) {
+        continue;
+      }
+
       if (!title.empty() && !MatchPattern(web_contents->GetTitle(),
                                           base::UTF8ToUTF16(title)))
         continue;
@@ -1185,6 +1196,11 @@ bool TabsUpdateFunction::RunAsync() {
     tab_index = tab_strip->GetIndexOfWebContents(contents);
   }
 
+  if (params->update_properties.muted.get()) {
+    bool muted = *params->update_properties.muted;

[not at google - send to devlin, 2015/05/26 23:09:46]

Could you make this (and I may have the names wrong here, and git cl format may
choose to change it):

const char* switch = base::Comment::switches::kEnableTabAudioMuting;
if (base::CommandLine::HasSwitch(switch)) {
  chrome::SetTabAudioMuted(contents, *params->update_properties.muted,
                           extension()->id());
} else {
  WriteToConsole(
      WARNING,
      base::StringPrintf("Failed to update mute state, --%s must be enabled",
                         switch));
}

[Jared Sohn, 2015/05/27 14:52:02]

Done (after making a few changes including not naming the variable 'switch' ;)).

It looks like the motivation here is to turn off muting if the flag isn't set. 
Should there also be a flag for turning on/off the API changes?  (The creating
new APIs website
(http://www.chromium.org/developers/design-documents/extensions/proposed-chang...)
indicates such but here we are modifying an existing API instead of creating a
new one.  It seems straightforward to remove the new fields from the tab object
and to disable c.t.update (like we do here), but it isn't clear to me how to
remove them from c.t.onUpdated and c.t.query.)

[not at google - send to devlin, 2015/05/28 23:04:42]

Nah no need for a separate flag. I think the API can just be written once and
when tab muting is enabled, the API can start working.

An interesting question is actually whether using the API should automatically
enable tab muting; in other words, is the flag designed for the ability of tab
muting, or is it for the UI? If just the latter, we should give the API free
reign. mui?

[miu, 2015/05/28 23:36:59]

It's designed to report whatever state the WebContents is in, whether muting is
being controlled from the UI or an extension via this new API.  I think the
simple answer is, yes, the API should get free reign.  We're still discussing
(behind-the-scenes) whether muting will become a permanent member of the tab
strip UI.  ;-)

[not at google - send to devlin, 2015/05/29 21:28:15]

Awesome. In that case we should actually be able to remove the command line
checks from everywhere?

+    chrome::SetTabAudioMuted(contents, muted, extension()->id());
+  }
+
   if (params->update_properties.opener_tab_id.get()) {
     int opener_id = *params->update_properties.opener_tab_id;