After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 524934 - Time slider widget fails to lose focus when cursor leaves handle
Time slider widget fails to lose focus when cursor leaves handle
Status: RESOLVED DUPLICATE of bug 477529
Product: totem
Classification: Core
Component: Movie player
2.20.x
Other All
: Normal minor
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-03-29 10:13 UTC by Timothy Goh
Modified: 2008-03-29 14:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Timothy Goh 2008-03-29 10:13:44 UTC
Please describe the problem:
During playback of an audio clip or movie, if the time slider handle is clicked and dragged, and the cursor leaves the handle, the handle remains selected even if the mousebutton is released. Moving the cursor along the x axis now causes the time slider to move along with it.

Steps to reproduce:
1. Start playback of an audio or video in Totem Movie Player
2. Click on the time slider handle and hold down primary mouse button
3. Drag slider to another position
4. Without releasing primary mouse button, move cursor away from slider (perhaps to top of screen)
5. Release primary mouse button



Actual results:
Time slider moves along with cursor even when the mousebutton is released and not within slider.

Expected results:
Slider widget should lose focus, and no longer be selected

Does this happen every time?
Problem is repeatable

Other information:
Problem replicated on Ubuntu 7.10's pre-installed Totem Movie Player.
Comment 1 Philip Withnall 2008-03-29 14:43:11 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 477529 ***