Closed Bug 1571 Opened 26 years ago Closed 25 years ago

Firing of links and buttons should trigger off of onclick

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P2)

All
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: joki, Assigned: joki)

Details

Links and buttons should not have to maintain their own internal state to fire clicks. They should be triggering off of the click event being fired by the event state manager.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA Contact: 4015 → 3847
QA contact re-assigned according to the product areas we're currently working on.
Target Milestone: M4 → M5
Links do this now. Buttons don't yet but this is just an internal thing. I'll fix it for M5.
Target Milestone: M5 → M6
Target Milestone: M6 → M7
This is a minor code fix. Moving out to M7
Target Milestone: M7 → M8
Target Milestone: M8 → M9
Still just a minor nit on my part. Not something needing to be on the M8 list.
Target Milestone: M9 → M14
A quick grep through the code shows lots of unnecessary usage of the mouse button up message instead of the mouse click message. But since this is a nice to have and not a necessity I'm pushing it out on my milestone list and I'll see if I ever have time to clean this stuff up.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
All of the instances of this that I was concerned about are now fixed with the new gfx stuff. I'm going to mark this fixed. This is code level so just trust me.
Status: RESOLVED → VERIFIED
Thanks, I trust you. Marking verified.
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.