Say Goodbye to native "OK Google" voice integration in Chrome on the desktop
Talking to Google while using Chrome on the desktop has become a tad harder in Chrome 46 as the company has removed the native integration of its voice control service Ok, Google from the web browser.
That does not mean that Chrome users cannot use their voice anymore to search on google as the option to do so is still baked in to the web service. The main difference is that you need to click or tap on the microphone icon first on pages supporting it before you can fire off voice searches or commands.
Google started to roll out voice search back in 2011 for the first time on Google.com, then in 2013 as a browser extension for Google Chrome, in 2014 as a native feature in Chrome, and rather recently also as a binary component in Chromium on Linux.
The integration allowed users to initiate voice commands with the words "OK Google" followed by the command itself, for instance to find something on Google Search or open popular websites. The browser listened to user commands when new tabs were opened in the browser or on Google.com.
Google was criticized by privacy advocates for integrating the "eavesdropping extension" natively into the Chrome browser. One concern that users expressed over and over again was that everything you said after using the hotword activation was sent to Google.
The company stores all voice interaction with its service on company servers, and we recently showed you how to open that archive and play back all of your voice interactions with Google on it.
A bug discovered in 2014 that allowed websites to listen in to everything said even after closing them did not instill confidence either.
The reason for the removal is lack of use according to Venturebeat which should not come as a surprise. While it may be beneficial at times to talk to mobile phones, considering that typing requests is not as comfortable as on a desktop, the same cannot be said for desktop use.
Other reasons include privacy, the lack of microphones on some setups to the list and that it feels less natural to speak to your computer than speaking to a mobile device.
Google removed "OK Google" voice search from Chrome for the desktop only. This means that the feature remains part on Android and on Chromebooks
OFF-TOPIC: ARTICLE SUGGESTION FOR MARTIN
On at least Windows 10, User Account Control has an additional policy that is enabled by default titled “User Account Control: Switch to the secure desktop when prompting for elevation”. This overrides the policy that has existed since Vista, “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode” since setting it to a behavior that doesn’t also trigger the secure desktop will be ignored and open the prompt in the secure desktop anyway.
This was likely done to work around bugs, since disabling the secure desktop may lead to failure in loading the prompts of the Consent UI or Credentials UI (an example of this is when the user has set “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode” to “Prompt for consent” or “Prompt for credentials” and “User Account Control: Switch to the secure desktop when prompting for elevation” to Disabled, then tries to stop receiving Insider builds in the Windows Update settings; the Consent/Credentials UI prompt sound effect will play but the prompt itself will not appear).
The secure desktop exists to isolate the prompts from the user’s desktop in order to avoid other software (in most cases, malware) from hijacking the prompts or tricking the user into accepting elevation from a fake prompt that masks itself as a real prompt.