Form autocomplete seems to trigger after two characters are entered. Aside from needing another way to trigger it (like IE has... down arrow or double click), I've found a bug in the method it triggers with currently. Go to a form you have lots of saved data for. Google will probably work. Enter "t<backspace". Input line is now empty, but Phoenix shows you all saved entries that start with t. (Works with any letter, of course). This is actually a handy workaround to not being able to trigger autocomplete any other way for a single letter.
Summary: backspace counts as second char and triggers autocomplete → clearing form field (e.g. with backspace) should cancel autocomplete
Resummarizing, because in IE, backspacing to turn "fo" to "f" does not cancel autocomplete, but backspacing to turn "f" into "" does cancel autocomplete.
Just wondering if this is still a problem for Linux users? A similar bug, bug 212487, which addressed the issue on windows was fixed on 2003 07 12. It WFM on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030728 Mozilla Firebird/0.6.1.
aww, now there's no way to view all the data for a form. Yes, this is fixed now, I'm assuming by the one-character-behind checkin.
OK maybe this can be marked as FIXED or WORKSFORME based upon comment 3?
Taking QA. Sorry for the bugspam
QA Contact: asa → davidpjames
WFM Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030804 Mozilla Firebird/0.6.1
Fixed, based on own experience, comment #3 and checkin for bug 212487
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
verified with another build (20030808)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.