If some alert box is shown in onBlur event the form loses focus. The test cases on the above URL show it very well.
To bryner. Nice testcase!
Setting component to XPToolkit/Widgets, which according to http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser accepts bugs relating to focus issues. Not JS Engine -
-> 1.0, nominating for beta1.
nsbeta1- per Nav triage team. Yet another reason not to throw up alerts like this.
Bob, would this go in your "events shit that completely screws up development for this this browser and makes it hard to evangelize" category?
Mass-moving all Navigator team 1.0 nsbeta1- bugs to 1.1
This worksforme with linux build 2002-03-21-08...
I can't seem to access the author's test case for confirmation but I seem to be having the same problem. Here is an example: http://htmlgoodies.com/primers/jsp/Validfld.htm
Created attachment 99516 [details] testcase Attaching test case, the hosting server connectiong is very bad.
I came across this bug while searching for something else, but I noticed, that while mozilla (1.3b, 2003021008) works as expected in all tests, weird things accompany the 3rd test: Click the 1st field, then click its label. An alert pops up, as expected. Now, as you move your mouse towards the alert's OK button, the text in the main window gets selected. I see this on Linux (Debian testing), libgtk+-1.2.10.
This bug is also manifested on Windows 2000 Professional SP3 running Mozilla 1.5. It's playing havoc with some form validations I'm trying to to on a box-by-box basis.
This still worksforme on Linux. The Windows issue may be a separate issue...
My results: 1. Linux 1.6b nightly: all tests pass 2. Windows 1.4 release: all tests pass 3. MingW 1.6a nightly: fail a) tab from 1st input to 2nd input, input has partial focus - typing works, but no caret, selection or undo. b) click from 1st input to 2nd input ignored - window gets focus. Note that although the Linux 1.6b nightly has the lazy editor patch, I clicked in the 2nd input first to make sure that it had an editor.
4. Windows 1.5b release: fail, same as 3.
A coworker and I have just run across this bug... In the testcase, the 2nd test fails by not giving focus to the second field. This is happening on linux (2.0b2) and on windows (126.96.36.199). Also, changing it from onblur to onchange yeilds the same results (assuming you change the value in the first field)