Closed Bug 154738 Opened 22 years ago Closed 21 years ago

Can't type in URL bar after entereing bad file URL

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mozilla, Assigned: jag+mozilla)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a+) Gecko/20020626
BuildID:    2002062609

If I go to the URL bar and type a filename or path that doesn't exist, I get the
"does not exist, please check location" popup, and then hit escape.  Most of the
time after that, I can't type into the URL bar or other text boxes that might
have already been displayed.

Reproducible: Sometimes
Steps to Reproduce:
1.Go to http://www.google.com/
2.Enter /badname in the URL bar
3.Wait for the "The file could not be found..." popup.
4. Hit escape without moving the mouse.

Actual Results:  I can't type in the URL bar, or the text box.

Expected Results:  I should be able to enter text in the URL bar or text box.
Blocks: keydead
what windowmanager are you using (and what version)?  see bug 130480
-> Akkana, UNIX keyboard stuff
Assignee: aaronl → akkana
Blocks: atfmeta
If I understand correctly, this isn't a gtk key event issue; it's a request that
after the "not found" popup comes up then is dismissed, focus should be in the
urlbar rather than in the old document, since the user is obviously trying to
navigate by typing in the urlbar.  This seems like a reasonable request.  Does
this not happen on other platforms?  It's not a pointer-focus issue, since the
mozilla window is correctly focused, just not the right element in the mozilla
window.

Whoever is changing the focus away from the urlbar should stop doing that.

Bryner, do you have any idea why the focus is changing in this case?  Would you
be a reasonable owner for the focus issue, or should it go to the owner of the
dialog?
Assignee: akkana → bryner
Status: UNCONFIRMED → NEW
Ever confirmed: true
There is a 99% chance this is a dupe of 130480.

Bob Horvath: what window manager are you using and what version is it?
I'm not Bob, but I see this behavior in xfce 3.8.14 and in icewm 1.0.3, using
pointer focus in both cases, and in gnome sawfish 1.0.1 using click-to-type. 
(The latter two tests used moz 1.0, since my understanding is that this is not a
new bug so any moz version is a valid test.)
-> jag, cc bzbarsky.  Looks like we need to detect that an error happened in
BrowserLoadURL (navigator.js) and not focus the content area if it did.
Assignee: bryner → jaggernaut
(Sorry for not seeing this earlier) 

I am using Enlightenment (0.16.5), with "focus follows pointer sloppily".  I'm
may be misunderstanding what the discussion on focus is, but the problem is not
where the focus remains, but that I can't enter anything either into the urlbar,
or the Google text box. All textual input is lost.  I don't care whether the
urlbar gets focus immediately after hitting escape on the bad file URL, although
I agree it is good behavior.

I'll also add that with 1.0, the problem still remains.  Sometimes it will work
as it should, but creating a new tab and trying it in that window will get the
problem to show up again. It might be the case that a small mouse movement is
detected. If I create a new tab, I can't
get any input into the new tab via the keyboard. I can click on bookmarks, and
they load and I can follow links, but I cannot type anything.
but I can't type in the urlbal or any text boxes in the page.

One thing I hadn't noticed before, but if I let some other window have focus,
then get focus back, and it works.  So, if this is the basic location bar
problem that lots of people have had, then it is a very easy way to reproduce it.
The bug you're describing is that you want the URL bar focused automatically
after this error dialog.

The bug summary "Can't type in URL bar" is WORKSFORME. Just typing Accel+L,
Alt+D or click in the URL bar and start typing.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.