maemo.org Bugzilla – Bug 3298
Focus not set to location bar after Ctrl-L shortcut is used
Last modified: 2010-01-14 12:29:57 UTC
You need to
before you can comment on or make changes to this bug.
(Control Panel > General > About product)
STEPS TO REPRODUCE THE PROBLEM:
EXTRA SOFTWARE INSTALLED:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9)
Stupid numpad return key, submitting the form prematurely. You'll have to wait
for me to write proper description here. :-P
SOFTWARE VERSION: 4.2.2008.23-14
STEPS TO REPRODUCE THE PROBLEM:
1. Open browser
2. Wait for home page to load
3. Go to http://www.google.com/intl/en/ (I presses Ctrl-l, typed the address
and pressed enter)
4. Click "Advanced Search"
5. Press Ctrl-l
6. Type in another URL
Location widget should be active and the URL selected, allowing user to replace
current URL by trying a new one.
Current URL is selected, but typed text appears nowhere. Current URL is intact.
In some cases pressing ctrl-l will move cursor to address field without
selecting the address, but allowing editing the field. Switching to desktop and
back to browser triggers this condition. Pressing ctrl-l again won't do
anything. Usually after tapping on the renderer page (i.e. having the location
widget to lose focus) restores ctrl-l's functionality. Unfortunately I cannot
reproduce this behaviour reliably.
Finally, I don't remember experiencing any issues like this with Chinook. I
suspect this issue has something to do with browserd.
Very annoying and 100% different from behavior under Chinook. I have always
kept the toolbar hidden and use crtl-L to start typing a new address and now
that does now work. Even when text is bound for the text entry area other
accelerator keys do not work. Ctrl-A will not select the whole text area.
*** Bug 3449 has been marked as a duplicate of this bug. ***
Still no updates from the developers so far (also not internally). :-(
Also see https://bugs.maemo.org/show_bug.cgi?id=3592 - different bug(s), but
along the same vein of intermitten usability issues with Ctrl-L, Ctrl-F, and
No change with 5.2008.43-7, still happens, still annoying. This basically makes
turning off toolbar via "View->Show toolbar->Fullscreen" unusable.
*** Bug 4156 has been marked as a duplicate of this bug. ***
> STEPS TO REPRODUCE THE PROBLEM:
> 1. Open browser
> 2. Wait for home page to load
> 3. Go to http://www.google.com/intl/en/ (I presses Ctrl-l, typed the address
> and pressed enter)
> 4. Click "Advanced Search"
> 5. Press Ctrl-l
> 6. Type in another URL
> EXPECTED OUTCOME:
> Location widget should be active and the URL selected, allowing user to replace
> current URL by trying a new one.
> ACTUAL OUTCOME:
> Current URL is selected, but typed text appears nowhere. Current URL is intact.
This can be reproduced in Fremantle. Following the steps above the focus
appears in the first field of the form. Pressing Ctrl-L does nothing: you need
to tap the location widget to move the focus there.
(In reply to comment #7)
> This basically makes
> turning off toolbar via "View->Show toolbar->Fullscreen" unusable.
Yes, you need to leave fullscreen mode if you want to type a new URL.
*** Bug 3622 has been marked as a duplicate of this bug. ***
Ctrl-L has been dropped from the shortcuts specification and should not be
mentioned anymore in Fremantle Web browser UI specification, hence this is
INVALID by definition in Fremantle (int-99106), or WONTFIX as for the normal
user not knowing about Nokia's specs...
(In reply to comment #11)
> Ctrl-L has been dropped from the shortcuts specification and should not be
> mentioned anymore in Fremantle Web browser UI specification, hence this is
> INVALID by definition in Fremantle (int-99106), or WONTFIX as for the normal
> user not knowing about Nokia's specs...
Boo! Hiss! This would make life so much easier and save so many useless taps
when in fullscreen. Reopening because I'm tired of spec-based idiocy.
Web browser specification has been changed recently and we have restored the
ctrl + L shortcut key. Some future version should have this fix.
I take it that there is absolutely no hope of getting this fixed for Diablo.
Thanks a lot for correcting! Wasn't aware of that internal ticket.
No, as Maemo4 is in maintenance mode and Nokia will only provide bugfixes for
critical issues, if at all.
For your interest the Mer project aims to provide a community backport of
Maemo5 for N8x0 devices. See http://wiki.maemo.org/Mer for more information.
This has been fixed in the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update