Closed
Bug 167195
Opened 22 years ago
Closed 17 years ago
Focusing form text elements does not fire onfocus handler
Categories
(Core :: Layout: Form Controls, defect, P4)
Core
Layout: Form Controls
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: rsh, Assigned: john)
References
()
Details
(Whiteboard: [jk-event][jk-focus])
User-Agent: Mozilla/4.79 (Macintosh; U; PPC) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1) Gecko/20020826 When form text elements (input text and text area) focused, focus handler is not activated. Reproducible: Always Steps to Reproduce: 1.Load testcase URL. 2.Click on checkbox, text elements, and document body to move focus around. 3.Window status area will display updated event target, currentTarget, and activation counter, as reported by a window-level onfocus handler. Actual Results: Focus is effective for form elements and keys can be typed in, but window-level onfocus handler is not activated. Other elements activate handler as expected. Expected Results: All elements, including text elements, should activate window-level on-focus handler when focused. In NS 4.79, focusing the text elements activates the onfocus handler as expected (although the checkbox element and document body don't do so). So some existent pages will stop working.
Comment 1•22 years ago
|
||
Looks like we never bubble those focus events out of the textbox and textarea.... Same on Linux.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac System 9.x → All
Hardware: Macintosh → All
Assignee | ||
Comment 2•22 years ago
|
||
Note that IE does not do this.
Priority: -- → P4
Whiteboard: [jk-event]
Target Milestone: --- → Future
Assignee | ||
Updated•22 years ago
|
Whiteboard: [jk-event] → [jk-event][jk-focus]
Comment 3•20 years ago
|
||
See discussion in bug 4033 -- focus events should not bubble.
Depends on: 4033
Comment 4•17 years ago
|
||
Can't load the testcase. And per DOM Events, focus and blur events should not bubble. I'd say this is INVALID.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•