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 593556 - Controls not shown in non-fullscreen mode
Controls not shown in non-fullscreen mode
Status: RESOLVED FIXED
Product: totem
Classification: Core
Component: Browser plugin (obsolete)
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: totem-browser-maint
totem-browser-maint
: 581511 591150 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-30 12:10 UTC by Robin Stocker
Modified: 2009-09-03 15:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robin Stocker 2009-08-30 12:10:26 UTC 
When I open a video file in the browser and the totem plugin handles it, the controls are not shown (any more). When the video is watched in fullscreen, the controls are available. So the user has no possibility to pause or see the progress in non-fullscreen mode.

Can someone confirm this? Is it a regression?
Comment 1 Bastien Nocera 2009-09-03 13:12:10 UTC 
This will only happen if you're viewing a mime-type handled by the VLC (Cone) plugin. VLC defaults to having its controls hidden, so we were mimicking that.

That obviously doesn't work well when we're handling mime-types that other plugins would be handling, such as mp3, or mpeg.

commit 149a572a2b11517a7cde9a73f44af0bf947428f3
Author: Bastien Nocera <hadess@hadess.net>
Date:   Thu Sep 3 14:11:16 2009 +0100

    Bug 593556 - Controls not shown in non-fullscreen mode
    
    Show the controls when VLC mode wasn't explicitely asked.
Comment 2 Bastien Nocera 2009-09-03 14:29:52 UTC 
*** Bug 581511 has been marked as a duplicate of this bug. ***
Comment 3 Robin Stocker 2009-09-03 15:06:46 UTC 
Just for the record, I was playing an OGV.

(Sorry for the duplicate by the way.)
Comment 4 Bastien Nocera 2009-09-03 15:47:45 UTC 
*** Bug 591150 has been marked as a duplicate of this bug. ***