Closed Bug 5944 Opened 25 years ago Closed 25 years ago

[BLOCK]ender- Mouse Events don't work with *GFX* OPTGROUP or OPTION elements

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: hyatt, Assigned: kmcclusk)

References

Details

(Whiteboard: [PDT+]Need this in M10)

The onchange handler for SELECT elements fires at the wrong time.  It is being
fired when the mouse is clicked in the SELECT element, which seems to just be
wrong.

It should be fired when the element loses focus AND has changed since last
gaining the focus.  This is specified in the DOM Level 2 working draft and also
in the JavaScript 1.2 Reference on developer.netscape.com.
Summary: onchange handler on SELECT elements fires at the wrong time. → [BLOCK] Mouse Events don't work with SELECT elements
Summary: [BLOCK] Mouse Events don't work with SELECT elements → [BLOCK] Mouse Events don't work with SELECT or OPTION elements
You can't attach simple click handlers to SELECT elements.  The click handler on
the SELECT element never fires.  Moreover, a click on a child OPTION element
never bubbles up, either to an OPTGROUP or to the SELECT.  I am assuming that
all mouse events are broken.

Take a look at the HTML4 spec on w3.org to see the set of events that
SELECT, OPTGROUP, and OPTION should be prepared to respond to.

This is a high priority bug, since between the inability to register click
handlers, and the disfunctional onchange handler, we have no way of using combo
boxes as reliable widgets.
You can't attach simple click handlers to SELECT elements.  The click handler on
the SELECT element never fires.  Moreover, a click on a child OPTION element
never bubbles up, either to an OPTGROUP or to the SELECT.  I am assuming that
all mouse events are broken.

Take a look at the HTML4 spec on w3.org to see the set of events that
SELECT, OPTGROUP, and OPTION should be prepared to respond to.

This is a high priority bug, since between the inability to register click
handlers, and the disfunctional onchange handler, we have no way of using combo
boxes as reliable widgets.
Assignee: karnaze → pollmann
Target Milestone: M7
Target Milestone: M7 → M6
Reassigning to Pollmann. Please solicit help from Pixley if needed.
Severity: normal → blocker
Changed severity to "blocker". It certainly is for the Editor, and probably is
for other groups as well
*** Bug 5936 has been marked as a duplicate of this bug. ***
Summary: [BLOCK] Mouse Events don't work with SELECT or OPTION elements → [BLOCK]ender- Mouse Events don't work with SELECT or OPTION elements
Status: NEW → ASSIGNED
I'll be trying to get most of this in M6.
The OnChange behaviour is reported as bug 3322.

OnClick works fine for me on SELECT listboxes.
http://blueviper/forms/onclick.html

OnClick for SELECT comboboxes works in the text entry field but not the
drop-down list.  This should be also fixed for M6.
http://blueviper/forms/onclick2.html

Mouse events on options and optgroups are not handled at all right now and I
haven't done work to assess them yet - so they may not make it into M6.
Summary: [BLOCK]ender- Mouse Events don't work with SELECT or OPTION elements → [BLOCK]ender- Mouse Events don't work with OPTGROUP or OPTION elements
Target Milestone: M6 → M7
I've made note of the fact that mouse events on the drop down list of a combo
box don't get bubbled up (or in fact ever enter the event system) in bug 3322.

The only remaining issue for this bug not covered by 3322 is that events don't
get routed to options or optgroups, but instead start out at the select.
Target Milestone: M7 → M12
This remaining problem should go away when GFX widgets become the default.

Postponing this one until "much later"
Blocks: 11346
Whiteboard: Need this in M10
Need this early in M10!
Assignee: pollmann → kmcclusk
Status: ASSIGNED → NEW
Summary: [BLOCK]ender- Mouse Events don't work with OPTGROUP or OPTION elements → [BLOCK]ender- Mouse Events don't work with *GFX* OPTGROUP or OPTION elements
I'm splitting this bug, one for GFX widgets (which should be fixed ASAP) and one
for native widgets (which is low priority and may not get fixed right away if
ever).  Since this is the bug with the most history, I'll leave this as the GFX
bug.  Reassigning Kevin McCluskey.  I'll hold on to the Native bug 11797 just as
a bookmark.
Status: NEW → ASSIGNED
Target Milestone: M12 → M10
Moving to M10
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
gfx selects enabled as default as of Aug 19, 1999 4:00PM.
Status: RESOLVED → VERIFIED
http://blueviper/forms/onclick.html seems to have a javascript error ('dump not
defined') and it does nothing in 4.7 or 5.0.
http://blueviper/forms/onclick2.html tells me that onclick is working.
I suppose that means that this is fixed for gfx widgets. Marking verified.
Whiteboard: Need this in M10 → [PDT+]Need this in M10
Putting on [PDT]+ radar.
No longer blocks: 11346
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.