Bug 67693 - Buttons are not released if they are hidden before release
Summary: Buttons are not released if they are hidden before release
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml ecma (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-09 18:45 UTC by Oded Arbel
Modified: 2007-02-25 15:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Test case (977 bytes, text/html)
2003-11-09 18:45 UTC, Oded Arbel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oded Arbel 2003-11-09 18:45:16 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.3.1 
OS:          Linux

When a button is pressed, its onclick event is triggered. if that event causes the button to stop being displayed (for example, by changing the "display" or "visibility" setting of the button or one of its containing blocks") then the button graphic is never "released" even as the mouse button is released. 
While the button 'onmouseup' event is fired correctly, the graphic is not updated and as a result, when the button is again displayed, the button graphic looks "pressed" until the mouse is moved over it.

See the test case attached - click "Open" to open the hidden element, then click "Close" to close it. when "Open" is clicked again the "Close" button graphic looks "pressed".
Comment 1 Oded Arbel 2003-11-09 18:45:57 UTC
Created attachment 3105 [details]
Test case
Comment 2 Tommi Tervo 2006-03-05 17:48:35 UTC
Seems to be fixed, works fine with pre 3.5.2 konqueror
Comment 3 Oded Arbel 2007-02-25 15:41:05 UTC
Might be related to the fix in Bug 68438, but currently the behaviour is that the button releases too early - less then half a second after the mouse button was clicked and before the mouse button was released. 

I've opened another bug report on this - Bug 142182. I need to come visit this again if 142182 will be fixed.