Closed
Bug 255481
Opened 21 years ago
Closed 21 years ago
Input fields not focusable after an onBlur Alert on window switch
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 134293
People
(Reporter: alex.purins, Assigned: jag+mozilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040812
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040812
If an input field throws an Alert ONBLUR as focus is moved away from the browser
window, then on return the Alert requires two presses of OK, and no input field
will accept focus.
Switching away from the window and back then does not throw an Alert, and
returns to normal behaviour.
May be a dup, because there are numerous focus and alert bugs logged, but did
not see one that matched this.
Reproducible: Always
Steps to Reproduce:
1. Render the following HTML
<input type=text name=n1 onblur='javascript:alert("blurred")'>
<input type=text name=n2>
2. Click in the first field so it has focus
3. Click outside the window so it loses focus and throws the Alert
4. Click back, dismissing the Alert (takes two clicks on OK)
Actual Results:
For three keystrokes, status bar showed 'Link not found: "1"' then "12" then "123"
On fourth keystroke, "Find stopped." appeared
Input fields, inluding location bar, could not be focussed
Switching away from window and back again restored function (without throwing Alert)
Expected Results:
Accept focus and keying into the input fields and location bar
Switching away from the field by Tab to the next, or clicking elsewhere in the
window, correctly throws the Alert and continues normally.
IE throws the Alert with no problems.
Opera has no problem because it does not throw the Alert when switching away
from the window, only when changing focus within the window.
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 134293 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•