User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141113143407 Steps to reproduce: updated to firefox 34. tried to login at usaa.com (https://www.usaa.com/inet/ent_logon/Logon). the text boxes for "online id" and "password" were not visible. however, 1password was able to find them and enter the required values. the text box for pin was also not visible but 1password filled that in, too. the text box for "security question", which is asked every time after upgrading the browser, was also not visible. 1password was not able to help there. could not enter the required text as i was unable to find somewhere to type. the text box for "online id" is coded by usaa like this: <div class="invisible_border"> <input id="usaaNum" class="login_input input_rounded_corners" type="text" aria-labelledby="messageLoginErrorLabel usaaNumLabel" aria-required="true" onkeypress="removeErrorMessageDiv()" onkeydown="jChangeFocus(event);" maxlength="20" size="25" name="j_username"> </div> Actual results: unable to fill in the requested "security question" and therefore unable to access my bank account. downgraded to firefox 33.1.1 Expected results: text boxes that were visible in firefox 33 should remain visible in firefox 34. you should be able to reproduce this even without an account at usaa. it's possible one of my many browser plugins or the cruft from my ancient firefox/mozilla installation (been using this software for decades) is responsible. given access to my bank is critical, debugging your browser is something i'd undertake reluctantly.
1password is broken with FF34. Could you test 1) in safe mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode 2) and with a clean profile: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Wrong link for profiles: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
okay, looks like the issue is a browser plugin. the keyfixer 0.5 plugin. i'm marking this as resolved invalid. bizarre thing is the keymappings that keyfixer is supposed to enable (home/end key behaviour) are still working. is that now a browser default? thanks
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.