Closed Bug 58441 Opened 24 years ago Closed 4 years ago

onFocus does not stop firing, effectively freezing app

Categories

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

All
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bugzillaabuse, Unassigned)

References

()

Details

(Whiteboard: [linux-only])

Attachments

(4 files)

Happens in: Linux 6.2 10-29-09 Does not happen in: MacOS 10-29-09, Win98 10-29-16 Reason for Severity: Essentially crashes the app-onFocus does not stop firing. Reproducible: Yes Steps to Reproduce: 1. Open testcase: http://bugzilla.mozilla.org/showattachment.cgi?attach_id=18280 2. Click inside text area 3. Try to dismiss window Actual Results: Damn thing won't go away Expected Results: Damn thing to go away
adding crash and RTM KWs. RTM just because if an onFocus event crashes the linux app I could see that as being a stopper. This is not, I repeat, not a recent regression, and happens as far back as 09-29-09 on Liinux (which is the oldest build I have on there). Per Hixie, it seems like you could easily crash Mail in there if you were to send someone this button. This bug encompasses any onFocus event not attached to a link (i.e. if you get sent to another page, it doesn't continue firing-focus ends up being washed away). I suspect this bug is also related to http://bugzilla.mozilla.org/show_bug.cgi?id=58440 as well. It takes down any open windows in the app, and also the terminal window that opened it. Very bad.
Keywords: crash, rtm
Marking rtm need info and re-assigning to Heikki because joki's Linux box isn't set up yet.
Assignee: joki → heikki
Whiteboard: [rtm need info]
FWIW, Button onFocus also fires forever. Also, FWIW, onFocus on the Mac fires twice. Doe this qualify as the same bug with slightly different characteristics on two different platforms(i.e. does not crash on Mac-only fires twice) ? Assuming so, changing Plat/OS to ALL. Win NT/98 have no problems.
OS: Linux → All
Hardware: PC → All
Using Commercial release (branch) build 2000-10-31-14 on Linux I can dismiss the alert window. I got a new alert window a couple of times, but then it did not reappear. However, clicking in the textarea again, or clicking anywhere on that window got the alert. I was able to switch to other windows without a problem. Switchiingh back got the alert. When I clicked "My Netscape" toolbar icon I got the alert & crashed.
Hmm, Johnny has differnt window manager than I. If he set focus follow mouse he did not see this problem: he saw that once you clicked the ok in alert he was not able to click on any toolbar icons. When he changed to "normal" focus he did get the infinite alert boxes. He also found that they are not really modal (for example, you can type in the textarea and if you have other mozilla windows open you can type in the urlbar of those even though nothing else seems to react).
Given that this: a) can cause crash equivalent condition only on Linux b) does not cause this every time c) is a problem only when an alert box is opened by onfocus handeler I will rtm- this. You can see that c) is true if you add an element like: <p id="id1">empty</p> and change the onfocus handler to document.getElementById('id1').firstChild.nodeValue='This dialog is displayed by a onfocus event' you will not get into a crash equivalent condition.
Whiteboard: [rtm need info] → rtm-
Back to joki. This is probably a dup of some bug on your list. After dismissing the alert the focus seems to go back to the textarea which again triggers alert etc. Weird thing is it does not happen all the time with me.
Assignee: heikki → joki
Changing crasher bug milestone to mozilla0.9.
Target Milestone: --- → mozilla0.9
Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
Summary: onFocus does not stop firing → onFocus does not stop firing, effectively freezing app
This is going to have to wait for 0.9.1. In discussions with saari we still haven't decided on the right solution.
Target Milestone: mozilla0.9 → mozilla0.9.1
Moving to M0.9.2. Joki is overloaded, this one can wait until after nsbeta1.
Target Milestone: mozilla0.9.1 → mozilla0.9.2
*** Bug 80786 has been marked as a duplicate of this bug. ***
QA contact updated
QA Contact: gerardok → madhur
Moving lower priority bugs out of .9.2 milestone.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Works for me on Windows. anyone else?
Missed 0.9.3.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
->0.9.5
Target Milestone: mozilla0.9.4 → mozilla0.9.5
-> 0.9.6
Target Milestone: mozilla0.9.5 → mozilla0.9.6
0.9.6 has passed, moving to 0.9.7. Load balancing 0.9.7 list shortly
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Moving bugs from 0.9.7 for triaging in 0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
nominating it as nsbeta1, because it would be a good bug to take in MachV
Keywords: nsrtmnsbeta1
Whiteboard: rtm-
*** Bug 67317 has been marked as a duplicate of this bug. ***
When I go to the testcase URL and click in the textarea field, I get a dialog saying "This dialog is displayed by an onfocus event". Press OK and the dialog reappears (presumably because the textarea field again gets focus) ... etc etc. Is this expected behaviour? Does *not* crash Mozilla. I'm using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214. Window manager is IceWM.
Keywords: nsbeta1nsbeta1-, topembed
Target Milestone: mozilla0.9.9 → mozilla1.0
Target Milestone: mozilla1.0 → mozilla1.1
Tested using the following: Netscape 03_22_05_trunk build Mfcembed 03_22_11_trunk build Mfcembed 03_22_11_0.9.9. branch build Problem is happening with TEXTAREA, INPUT/password, INPUT/text, INPUT/file and INPUT/image (attached testcases). Unable to lose focus. When you click on the alert button, element still has focus. If you click on another application and then come back, alert box will get generated again.
Attached file INPUT/text testcase (deleted) —
Attached file INPUT/password testcase (deleted) —
Attached file INPUT/file testcase (deleted) —
topembed-, you won't see things like this in the wild (you can't interact with the form)
Keywords: topembedtopembed-
QA Contact: madhur → rakeshmishra
*** Bug 162936 has been marked as a duplicate of this bug. ***
A test suite has been created to track bug 58441, bug 134293, bug 164686, bug 105129, bug 131843, bug 50221, bug 134321, bug 122311, and bug 112294: http://bugzilla.mozilla.org/attachment.cgi?id=100778&action=view People who have reported problems in the bugs mentioned please perform all the test in this suite. All bugs will be resolved as duplicate of the appropriate bug unless someone can reproduce a problem with onblur/onfocus style change (no alert involved)
->bryner, but not high priority
Assignee: joki → bryner
Whiteboard: T2
QA Contact: rakeshmishra → trix
WFM build 2002122704, Windows XP, I dismiss the alert and focus is back on form field with no more alerts.
As per my comment 6 in bug 197919, I also managed to stumble upon this bug when I created the popup window tester. As when I focus on the input field, it continuously fires the onFocus event in effect never letting me close the popup window.
This bug still present in the Firebird 0.7.1 and very annoying. Any chances to have this fixed soon since this issue is open for a *very* long time. -aj
*** Bug 220779 has been marked as a duplicate of this bug. ***
Blocks: 122311
Still no problem in Windows XP, but sounds like this should have some sort of priority considering the annoyance factor when it crops up. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316
Flags: blocking1.8a?
Expected results: 1. click on box with 0 in it 2. error window appears 3. click ok 4. error window appears 5. repeat until browser kill on command line Here is another case that locks my fedora linux firefox 0.8. I keep clicking okay and a new window appears before I can correct my mistake. I tried it on MacOSX and was able to get out of the loop. Possible correction: put one second pause inbetween click ok and new window appearing.
Flags: blocking1.8a? → blocking1.8a-
*** Bug 282820 has been marked as a duplicate of this bug. ***
Is this still a bug? I'm testing with 1.7.6 build 20050319 and it looks like the behavior is correct. The only time I can see onFocus fire again is if I leave the form field focused, click to another window and click to the browser window with the form field.
*** Bug 49986 has been marked as a duplicate of this bug. ***
*** Bug 332563 has been marked as a duplicate of this bug. ***
The bug still exists - but only on Linux versions of FireFox.
*** Bug 336518 has been marked as a duplicate of this bug. ***
(In reply to comment #42) > The bug still exists - but only on Linux versions of FireFox. Granted this bug is fixed in W2K version of Firefox 1.5.0.2, but still persist in Linux and Mac OS X versions.
Assignee: bryner → events
QA Contact: trix → ian
Target Milestone: mozilla1.1alpha → ---
Upon mail pinging from: Wayne Mery <vseerror@lehigh.edu> > pinging Dragan... > > <https://bugzilla.mozilla.org/show_bug.cgi?id=58441> > > Hi. > Does this happens on a trunk build? I've just tried nightly builds of Firefox, and situation changed a bit. Mac OS X version passes the first test (INPUT/text testcase), and it seems to be fixed in mac version. Unfortunately, Linux version still fails :( Thank you for your time and interest...
Keywords: hang
(In reply to comment #45) > > Unfortunately, Linux version still fails :( > I tested on Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy) and it does not hang or crash, however, the alert message does not stop firing (infinite loop). I also tested with Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.1) Gecko/20061010 Firefox/2.0 and it does not show the problem. This bug seems to be related to bug 358849 (another problem with onfocus and alerts). But, this bug does not work with Linux and works with Windows; the bug 358849 is the inverse.
So is it Linux only now ?
(In reply to comment #47) > So is it Linux only now ? Yes
OS: All → Linux
Keywords: crash, hang, topembed-
Whiteboard: T2 → [linux-only]
Assignee: events → nobody
QA Contact: ian → events
This bug (for example the attached "INPUT/text testcase") is still very much alive in Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.17) Gecko/2010010604 Ubuntu/8.10 (intrepid) Firefox/3.0.17 and Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a2pre) Gecko/20100211 Minefield/3.7a2pre
Component: Event Handling → User events and focus handling

Hi, I tried to reproduce this issue again on an Ubuntu 18.04 64 bit using the Release version of Firefox 85.0.2 but it works without issues.. Is there a specific version of Linux this issue occurs on ? does it still occur on your end ? or we can Close this one as Works for me until someone manages to reproduce the issue again ?

Flags: needinfo?(jstutte)

I would not know who to needinfo to ask, most of the involved people having this problem are not active any more on bugzilla, it seems. So I'll close this.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jstutte)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: