Closed Bug 130800 Opened 22 years ago Closed 20 years ago
HTML button 'forgets' its js set position when clicked
Over to DOM Events.
Assignee: jst → joki
Component: DOM Level 0 → DOM Events
QA Contact: desale → vladimire
Confirming bug, but there is nothing wrong with the click event. The problem seems to be that when the HTML button is depressed it temporarily moves back to its original location. If this location moves it out from under the cursor then the mouseup event doesn't happen on the HTML button, and hence the _click_ event naturally doesn't either. Also attaching reporters example.
Confirming and changing Summary.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Mouse left-click does not appear to fire button's onclick event consistently → HTML button 'forgets' its js set position when clicked
Confirming button behavior Click and hold mouse button down, and the HTML button jumps to the left. If the HTML button jumps out from underneath the mouse cursor, the onClick does not fire. If, while holding the mouse button down, you move the mouse, the button jumps back. Releasing the mouse button over the HTML button fires the event. Is this still DOM Event or is it something else?
This is wierd! Works fine on mac 7.01 release...
Assignee: joki → jkeiser
Still broken on Mozilla 1.3a, Linux. More strangeness: on depressing the mouse button, the form button at position b jumps to its original position a. Move the mouse one pixel, and the button jumps back to b. Move the mouse one more pixel, it jumps to a. Make little circles with the mouse cursor while the mouse button is depressed, and the form button flickers back and forth between position a and b.
Boris might be interested to see this. It's a relatively positioned button, almost certainly an incremental reflow problem.
This almost smells like some cached data is not being cleared out of the ruletree...
Boy, the behavior of the button in the testcase was correct in the 6/11/02 trunk build, but I can reproduce the bug in the 1/08/03 Trunk build in Windows.
This worksforme in current builds; probably fixed by bug 171830
Status: NEW → RESOLVED
Closed: 20 years ago
Depends on: 171830
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.