Closed Bug 243405 Opened 20 years ago Closed 6 years ago

Can't type in text fields after mozilla loses focus

Categories

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

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: loconet, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

In the attached testcase there is 2 input textboxes with onChange and onFocus
handlers, if you type something on the first box then start up another
application which has keyboard focus (ie: notepad) and then come back to the
mozilla window with the input boxes, you won't be able to click on any of the
input boxes nor the URL input bar nor any other text input control in mozilla.
Note, it does not hang the browser because you can still close tabs, close
mozilla, etc. If you go back to the application that was run and then go back to
mozilla, it all goes back to normal.



Reproducible: Always
Steps to Reproduce:
1. Type something on the first input textbox of the test case
2. Start up an application that has an input box (ie: notepad.exe)
3. Go back to the mozilla window with the input textboxes.

Actual Results:  
I'm unable to click/setfocus on any of the input text boxes or the URL input bar
or any other text input control in mozilla. 

Expected Results:  
I should be able to set focus and type on the text boxes

Able to replicate with:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Attached file Simple test case
Summary: Unable to set focus on Input boxes after mozilla looses focus to a different app → Unable to set focus on Input boxes after mozilla loses focus to a different app
Nothing to do with the JS engine.
Assignee: general → general
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → general
I can confirm it.
Also I'm getting an assertion (in a debug build) when I'm doing step 2:
ASSERTION: Attempt to decrement focus controller's suppression when no
suppression active!
: 'PR_FALSE', file c:/mozilla/mozilla/dom/src/base/nsFocusController.cpp, line 478
Mozilla 1.7branch 200040513 Windows 2003
It's more than that: I can't type in any textfield after mozilla loses focus
(can't type in the URL bar, in form fields), even in new tabs !
I'd change the summary to "Can't type in text fields after mozilla loses focus
to a different app"
I'm leaving this unconfirmed for now because I don't know what component to
reassign to
Flags: blocking1.7?
Keywords: testcase
Summary: Unable to set focus on Input boxes after mozilla loses focus to a different app → Can't type in text fields after mozilla loses focus
I can confirm this with a Firefox windows build from 5/18 and the latest Windows
branch SeaMonkey build. The workaround is to click the taskbar button for that
Mozilla window or to alt+tab to another app and back to Mozilla. Doing something
to refocus the window makes it functional again. 

Does anyone know when this regressed? There are archived nightly builds at
http://archive.mozilla.org/pub/ and if someone could track down the build where
it regressed, that'd go a long way toward getting this fixed.
Status: UNCONFIRMED → NEW
Component: Browser-General → Event Handling
Ever confirmed: true
Assignee: general → events
QA Contact: general → ian
It's very old.
I can see it on windows 2003-08-18-09-trunk
It also happens with Mozilla 1.4
Using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
, the problem of not being able to set focus/type in any textbox in the browser
does not happen. It does however force the second application to automatically
loose focus and focus is forced back to the browser and to the 2nd input box. 
Johnny, can you take a look at this?
Flags: blocking1.8a2?
Flags: blocking1.7?
Flags: blocking1.7-
bryner, does the assertion in comment 3 ring any bells?
Tested this on Mac an Linux with Firefox 0.9+ branch builds and did not have
this problem.
Flags: blocking1.8a2?
This is wfm with current trunk build. 
Reporter could you please retest with current trunk build?
http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/
(In reply to comment #11)
> This is wfm with current trunk build. 
> Reporter could you please retest with current trunk build?
> http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/

Sorry about the delay.

I'm still seeing the problem with 

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050706
Firefox/1.0+
Yes, now I can reproduce the problem too. A resize of the Mozilla window seems
to fix the problem.
Assignee: events → nobody
QA Contact: ian → events
seems to work ok.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Component: Event Handling → User events and focus handling

Still doesn't work.

(In reply to MarjaE from comment #15)

Still doesn't work.

Same as Niel, I also don't reproduce this bug anymore. What's your environment? I tested on Windows, used start menu do open note.exe and used Alt - Tab to going back to Firefox.

Flags: needinfo?(erwinm)

I'm on MacOS 10.14.6. It works in the linked testcase. It doesn't work whe I'm typing and Firefox loses focus while I'm typing, e.g. half the time I use the Internet Archive and try to search their book collection.

Flags: needinfo?(erwinm)

P.S. Not so common these days, but that used to be really common for me. If it's just the original test case, then yes, worksforme makes sense.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: