|Issue 97502||Google Authenticator over BT does not work in web content|
|Starred by 5 users||Project Member Reported by email@example.com, Sep 21 2011||Back to list|
Chrome Version : 15.0.874.21 OS Version: OS X 10.6.8 What steps will reproduce the problem? 1. Navigate to http://www.google.com/ 2. Focus the search box. 3. Activate Google Authenticator over BlueTooth EXPECTED OTP is fetched, filled into search box. ACTUAL "Unable to get OTP" Note: OTPs are properly fetched if focus is, e.g., in the omnibox. This seems like it might be related to bug 90193 (and bug 95045). However, I verified that this works in Chrome 14 on Lion, which also has the bundle blocker active.
Sep 22 2011,
Move the BT library from /Library/ScriptingAdditions to /System/Library/ScriptingAddtions and then bisect.
Sep 23 2011,
Regression range: http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&range=97354:97365 Local testing confirms this is caused by [ http://src.chromium.org/viewvc/chrome?view=rev&revision=97362 ]. Looks like Google Authenticator needs to be updated correspondingly.
Sep 23 2011,
Sep 28 2011,
Pushed new version of Authenticator. Should auto update everyone.
Oct 13 2012,
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
Mar 11 2013,
|► Sign in to add a comment|