Closed
Bug 596007
Opened 15 years ago
Closed 7 years ago
Typed location is co-opted with first character of URL from open tab
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: ilatwm, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:2.0b5) Gecko/20100101 Firefox/4.0b5
Build Identifier: Mozilla/5.0 (Windows NT 6.0; rv:2.0b5) Gecko/20100101 Firefox/4.0b5
OBSERVED BUG:
The first character entered in the address/location bar is replaced with an "h" from the "http:..." of the first suggested result URL.
Reproducible: Always
Steps to Reproduce:
1) Log into Gmail in an app-tab
2) Open another, regular tab
3) Type the "m" of, e.g., mail.yahoo.com. -- The address bar is auto-filled with the selected URL associated with the first "Switch to tab" result of the Wonderbar suggestion for the Gmail app-tab.
4) Typing the remaining characters, i.e., "ail"; results in "hail", not "mail".
Actual Results:
typing "mail" in address bar, results in "hail"
Expected Results:
Allowing user to type a domain name starting with "m" without replacing it with an "h".
REGARDING CAUSE:
Have not be able to confidently identify what the exact cause is. I cannot reproduce the bug behavior with any other character I have had time to test than the "m". The open tab doesn't have to be Gmail, but the title or URL apparently must contain an "m", which somehow seems to cause the problem every time.
It seems as though I was wrong about the reproducibility, as the behavior did not appear on a different system last night. I have confirmed the behavior on two different systems running FFb5 and Identified an obvious work-around.
WORKAROUND:
Simply use the esc key to cancel out the false FF action, which will allow the user to continue entering the intended text without corruption.
Updated•14 years ago
|
Version: unspecified → 4.0 Branch
Comment 2•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•