Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 403187 - www-client/chromium html5 fullscreen video does not work
Summary: www-client/chromium html5 fullscreen video does not work
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Chromium Project
URL:
Whiteboard: ht-wanted
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-11 16:51 UTC by Sylvain BERTRAND
Modified: 2012-02-14 13:45 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info www-client/chromium (infos,4.89 KB, text/plain)
2012-02-11 16:51 UTC, Sylvain BERTRAND
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain BERTRAND 2012-02-11 16:51:12 UTC
Created attachment 301575 [details]
emerge --info www-client/chromium

html5 video player is not going fullscreen on youtube/dailymotion/vimeo, that on any video.
Comment 1 Julien Sanchez archtester 2012-02-13 13:14:25 UTC
Can't reproduce this problem with chromium-9999 (19.0.1040.0 (Developer Build 121661 Linux))

Could you try with this URL? http://html5demos.com/video
Comment 2 Sylvain BERTRAND 2012-02-13 15:53:55 UTC
I tried your link. Fullscreen does not work neither.
Comment 3 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2012-02-13 16:06:32 UTC
(In reply to comment #2)
> I tried your link. Fullscreen does not work neither.

http://html5demos.com/video + fullscreen worked for me with chromium-17.0.963.46 .

What exactly are your steps to reproduce? Can anyone else repro?
Comment 4 Sylvain BERTRAND 2012-02-14 13:45:01 UTC
found a pattern... for fullscreen with chomium or firefox you must have a window manager supporting some features (openbox does the trick), I have a forked light version of openbox (lboxwm) which do not support the requiered feature.

It should use a fullscreen method like the one mplayer uses, but:
http://code.google.com/p/chromium/issues/detail?id=42467

So it's an upstream bug.