I'm not sure what's the question here mpearson@. Can you clarify what you would like to know?

Regarding the Media.Audible.AddTab user action, it is recorded when a tab becomes audible. It is not related to the AddTab button.

I would like to know how often users click on the voice icon in the fake search box on the new tab page.

It sounds like you should use a user action for this. I don't see why not :)

I don't anything about how to implement this.  I have no knowledge of that part of the  code base.  Please don't reassign the bug to me.  I initially assigned the bug to you because I thought you worked on the voice area.  (You own a user action that gets triggered as a result of using voice search--the resulting page gets read out loud.)  If I'm wrong, can you please find the right person?  You're definitely close to this area than me.

thanks,
mark

I have no idea who works on voice search. This user action is related to media and the audible state of a tab. I'm surprised it's triggered for voice search but I've never use the feature so maybe it outputs sound. Either way, I'm afraid I can't help more.

CC kmadhusu@ - I know you're long past working on this kind of stuff, but perhaps you know who to direct this request to.  thanks!

Adding NTP team to triage; the desktop NTP is in their bailiwick now.

On the remote NTP, that'd be quite awkward to do, since voice search is handled purely by the page, without any direct interaction from Chrome. Let's do this once we have voice search on the local NTP, which will make things much easier.

"NewTabPage.VoiceActions" and "NewTabPage.VoiceErrors" histograms have been added for Voice Search on the local NTP, as of http://crrev.com/c/660126. See go/local-ntp-voice-search and go/ntp-refactor for more details.