Closed Bug 533287 Opened 16 years ago Closed 6 years ago

[Regression] n900: Letters auto-capitalize on url bar on first type

Categories

(Firefox for Android Graveyard :: General, defect)

Fennec 1.1
ARM
Maemo
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aakashd, Unassigned)

References

Details

(Keywords: polish)

Build Id: Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2b5pre) Gecko/20091207 Firefox/3.6b5pre Fennec/1.0b6pre Steps to Reproduce: 1. Open Fennec (make sure the auto-capitalization feature is enabled). 2. Click on the url bar 3. Type a letter or two Actual Results: The first letter typed in the url bar will be auto-capitalized Expected Results: The first letter shouldn't be auto-capitalized.
Step #2 is not needed - in fact, clicking on the urlbar will make the code work correctly in my tests. This bug occurs about 90% of the time for me when starting Fennec, awesomebar auto-displays, and start to type using keyboard.
tracking-fennec: --- → ?
This also happens if you bring up the symbol map while typing, when its dismissed, the next key entered will be capitalized.
I bet there is something to see with the window visibility and we failed somewhere here http://mxr.mozilla.org/mozilla-central/source/widget/src/gtk2/nsWindow.cpp#7043 I in _editURI i call gFocusManager.setFocus in a setTimeout the state is well updated and we do not enter uppercase char at launch
tracking-fennec: ? → 1.1+
Is it still blocking? Since we have a start page the user will likely click on the urlbar to go somewhere and clicking on the urlbar prevent the auto-capitalize bug/ So only case where this bug still happen is when the user choose to start on about:blank instead on about:home.
(In reply to comment #5) > Is it still blocking? Since we have a start page the user will likely click on > the urlbar to go somewhere and clicking on the urlbar prevent the > auto-capitalize bug/ This is true. The bug is less obvious now. > So only case where this bug still happen is when the user choose to start on > about:blank instead on about:home. There was talk of making about:blank _not_ open the awesomescreen. We need to nail down that decision.
Keywords: polish
(In reply to comment #6) > There was talk of making about:blank _not_ open the awesomescreen. We need to > nail down that decision. We did decide to _not_ open the awesomescreen for about:blank. This means that this bug is hard to reproduce. Removing blocking flag.
tracking-fennec: 1.1+ → ---
Component: Linux/Maemo → General
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.