Closed Bug 324510 Opened 15 years ago Closed 13 years ago
Form manager refuses to memorize my gmail e-mail address
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Firefox refuses to memorize my gmail e-mail address. Example: TheReg article feedback page. Ff memorized (and picked from other forms) all my other e-mails. Ff memorized my once misspelled address (gmaill.com instead of gmail.com). But. My proper gmail e-mail address - the same one used for the bugzilla account - is never memorized. I beleive it was the same on Ff 1.0x. Non critical - but *very* annoying. Reproducible: Always Steps to Reproduce: 1. Find some form on the net with e-mail address field. 2. Fill & submit the form 3. Go to step 1 and see all other fields having drop-down menu with completition options, except for the e-mail. Actual Results: E-mail address is not memorized. Expected Results: E-mail shall be saved and provided as compleition option. Any ideas as to what might be the cause are welcome.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 WFM
Deleting or renaming formhistory.dat in your profile will fix this I assume. http://kb.mozillazine.org/Profile_Folder
INVALID or WFM? Ihar, support is also available at http://forums.mozillazine.org/
One WFM & no response from reporter re: comment 2 -->INCOMPLETE. Reporter, if you still see this problem with Firefox 2 please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 1.5.0.x Branch
Ironically enough, it reappeared some week(s) ago on my /fresh/ Firefox 2.0x installation. (Fresh == 5-6 month or so.) Functionality is rarely used, so it is hard to spot when it happens. Probably it happens to other fields too. Hard to diagnose. I do not remember what/where I have typed - since I rely on Ff to remember it ;) I need my e-mail most - so it is easy to spot that obvious omission. Since the back-end is known to be undergoing a rework - and nobody else complaining - I do not see much sense reopening it.
You need to log in before you can comment on or make changes to this bug.