Closed
Bug 146066
Opened 22 years ago
Closed 20 years ago
[FIXr]should label element retarget events?
Categories
(Core :: Layout: Form Controls, defect, P1)
Core
Layout: Form Controls
Tracking
()
RESOLVED
FIXED
mozilla1.8beta1
People
(Reporter: dbaron, Assigned: bzbarsky)
References
Details
(Whiteboard: [whitebox])
Attachments
(1 file)
(deleted),
patch
|
bryner
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
This is a followup bug to bug 96813. In bug 96813 comment 14 it was suggested
that when the label element sends the event routed through its "for" element, it
should change the target of the event to the "for" element. See also bug 96813
comment 17.
Updated•22 years ago
|
OS: Linux → All
Hardware: PC → All
Updated•22 years ago
|
Whiteboard: [whitebox]
Comment 2•20 years ago
|
||
We shouldn't be "rerouting" events at all, we should be firing new ones.
Bug 271740 is one instance of this.
Assignee | ||
Comment 3•20 years ago
|
||
This makes us fire new events targeted at the right node, and only when we're
in the system event group (so it's the "default action" for the label). Doing
it only in the system event group fixes bug 276279 (we only SetFocus() once).
Attachment #170412 -
Flags: superreview?(jst)
Attachment #170412 -
Flags: review?(bryner)
Assignee | ||
Updated•20 years ago
|
Assignee: john → bzbarsky
Summary: should label element retarget events? → [FIX]should label element retarget events?
Target Milestone: Future → mozilla1.8beta
Comment 4•20 years ago
|
||
Comment on attachment 170412 [details] [diff] [review]
Fire new events
sr=jst
Attachment #170412 -
Flags: superreview?(jst) → superreview+
Updated•20 years ago
|
Attachment #170412 -
Flags: review?(bryner) → review+
Assignee | ||
Updated•20 years ago
|
Summary: [FIX]should label element retarget events? → [FIXr]should label element retarget events?
Assignee | ||
Comment 5•20 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
*** Bug 302686 has been marked as a duplicate of this bug. ***
Comment 7•19 years ago
|
||
Has this been checked in for Firefox yet? My bug 302686 got marked as a
duplicate but I'm seeing bad behavior in Firefox 1.0.6.
Assignee | ||
Comment 8•19 years ago
|
||
This was checked in for all Gecko consumers on 2005-01-20. Firefox 1.0.6 is
using a Gecko from 2004-04 with some security fixes.
You need to log in
before you can comment on or make changes to this bug.
Description
•