Build ID: just pulled When you mousedown on the button in the testcase I'll attach, the button does not depress, although the onclick event is fired upon mouseup. If you mousedown on the button and then drag away, this appears in the console: dragstart didnt get here ****** returning null 2 You shouldn't even be allowed to drag a button, so I don't know why this is happening.
Actually, this probably has less to do with dragging and more to do with the window.status (since the testcase doesn't work without it). So feel free to update the summary as necessary. cc'ing jst
This one belongs with Tom, I believe, reassigning.
Actually its the onmousedown intercept that killing the depression sequence. In order for the button to depress the mouse must be over the button and the mouse must be down. That way when you mouseout of the button it goes back up and so forth. So since the mousedown is getting taken at the <body> level to set the status the sequence is messed up. A minor bug, should be fixed in the next revision when we separate out the internal and external event handlers a bit more. Marking trivial since the button click still works. Marking future.
Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.
qa contact updated.
SPAM. HTML Element component is deprecated, changing to Layout component. See bug 88132 for details.
Come on Bugzilla, you can do it...
WFM on current Linux CVS. Can this be closed up?
WFM on 2004020311 win2k trunk.