Closed Bug 685643 Opened 13 years ago Closed 13 years ago

Starting to type the H in URL bar gets converted to letter W

Categories

(Firefox :: Address Bar, defect)

8 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 678352

People

(Reporter: northlayout, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows; Windows NT 5.1; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110906042008

Steps to reproduce:

Started to type the url which begins with the letter H.


Actual results:

The letter H gets converted to letter W.
This only happens when the first letter i type in the URL bar is the letter H.



Expected results:

The letter should have remained as letter H and not got converted to letter W.
I have checked this in safe mode so that i can be sure that no other add-on is creating any problems

I have found the reason for this issue.
The issue happens because the http:// prefix has been dropped in this build (i have not checked Ver 7 as this feature has been added in that version too).

When i toggle the entry "browser.urlbar.trimURLs" to false in the about:config page, the typed letter remains as letter H.
OS: Windows XP → Windows 7
Hardware: x86 → x86_64
This seems to be a duplicate of Bug 690244.
So the question is, do you have browser.urlbar.autoFill enabled?
Yes, browser.urlbar.autoFill is set to True.
I tried with browser.urlbar.autoFill set to False and i am not having this problem.


I have now updated my browser to V 10 nightly build now, and i am not able to replicate the problem. This seems to have been corrected in V 10. 
Have not checked V 9, but problem still exists in V8.
I had a look at the comments in Bug 690244 as described above.
This is indeed a duplicate of Bug 690244.

Please let me know if you need any more information.
(In reply to vashok1 from comment #3)
> Yes, browser.urlbar.autoFill is set to True.
> I tried with browser.urlbar.autoFill set to False and i am not having this
> problem.
> 
> 
> I have now updated my browser to V 10 nightly build now, and i am not able
> to replicate the problem. This seems to have been corrected in V 10. 
> Have not checked V 9, but problem still exists in V8.

Spoke too soon. Issue is persisting in Ver 10 also.
Marking as duplicate of Bug 678352 which is as yet, unfixed
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.