134293 - <input type=text> onblur event triggered multiple times and field goes dead

Status: RESOLVED WORKSFORME

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

Description

[Madhur Bhatia]

mfcembed 03/27/01 build -- 
ftp://ftp.mozilla.org/pub/mozilla/nightly/2002-03-27-23-0.9.9ec/embed-win32.zip

1. open testcase attachment 
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=76771
2. type something in textbox.
3. tab out of the text box.
---actual---
onblur event calls an alert box twice. Cursor returns back to the textbox and 
the user is able to type text in the textbox.
------------
4. repeat step 2
5. mouseclick out of the text box
---actual---
onblur event calls an alert box twice. the keyboard goes dead. the cursor does 
not return back to the textbox.
I am unable to click on the textbox. But, I am able to click on the browser url 
field.
------------

Comment 1

[Madhur Bhatia]

cc'ing mdunn and chrisd

this is partially a regression from 0.9.4 (netscaqpe 6.2 rtm)
1. in 0.9.4 the onblur event triggers an alert box just once.
2. in 0.9.4 the focus does not return back to the textbox, after clicking or 
hitting keyboard enter  on trhe alert box.

Comment 2

[Madhur Bhatia]

continue comment # 1

3. in 0.9.4, user able to click on textbox after closing the alert box. Keyboard 
does not go dead.

Comment 3

[Valerio Capello]

wfm build 2002032803 win98

after closing the alert box (which appears once) focus goes to the URL field,
but I'm able to click on the textbox and change text once again. I've tried it
several times and always worked. 

Comment 4

[Madhur Bhatia]

this bug is specific to the MFCembed build on win2000, 
which can be downloaded from 
ftp://ftp.mozilla.org/pub/mozilla/nightly/2002-03-27-23-0.9.9ec/embed-win32.zip

Comment 5

[Madhur Bhatia]

Attachment: testcase for <input type=password

see the same bug for <input type=password> on the MFCembed build.

Comment 6

[Daniel Wang]

*** Bug 134259 has been marked as a duplicate of this bug. ***

Comment 7

[Daniel Wang]

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)

Comment 8

[Pham]

http://bugzilla.mozilla.org/show_bug.cgi?id=179125#c3

joki is no longer here

Comment 9

[Frank Wein [:mcsmurf]]

*** Bug 255481 has been marked as a duplicate of this bug. ***

Comment 10

[:Gavin Sharp [email: [e-mail]]]

*** Bug 247359 has been marked as a duplicate of this bug. ***

Comment 11

[Philip Rinn]

> http://bugzilla.mozilla.org/attachment.cgi?id=100778&action=view
I run this test-suite and I had problems with
- Document onfocus test: alert() appeared 9 times, after that firefox is  
unuseable but does not crash
- Window onfocus test: alert() appeared 9 times but firefox ist still useable

the testcase for this bug WFM, but the testcase for Bug 247359 doesn't work for
me (http://bugzilla.mozilla.org/show_bug.cgi?id=247359#c1)

UA: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

Comment 12

[Mark de Jong]

Testcase still causes some freaky results in Firefox 3.0.7.
Firefox doesn't seem to like a blur in a blur event and the alert blurs the input.

When running the testcase sometimes keyboard input won't work in the <input> after tabbing away and going back. Sometimes the urlbar also temporary refuses keyboard input. But tabbing away and back again seems to fix the problem.

Seems related to bug #334784 and bug #53579 to me.

Comment 13

[Daniel Kirsch]

WFM in 3.6.7

Comment 14

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Firefox: 48.0a1, Build ID  20160403030243
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:48.0) Gecko/20100101 Firefox/48.0

I have tested this issue on the latest Firefox (45.0.1 - Build ID: 20160315153207) release, latest Nightly (48.0a1) build, but I can not reproduce it. I have tested this issue using the provided URL and test case from comment 0 and comment 5. At step 3, onblur event calls an alert box once and the cursor does not return back to the input field. I have repeated the steps a few times and I was able to click on the input field and typing from the keyboard worked properly. 

Considering the fact that I didn't manage to reproduce this issue and I'm unable to request more info from the reporter since the account is disabled, I will mark this as RESOLVED WFM. If anyone can still reproduce it, feel free to reopen the issue and provide more information.

Thanks,
Cosmin.