RESOLVED WORKSFORME38464
youtube html5 cannot seek or change volume 
https://bugs.webkit.org/show_bug.cgi?id=38464
Summary youtube html5 cannot seek or change volume
iddo
Reported 2010-05-03 07:46:50 PDT
Tried in midori and google-chrome browsers, the controls for seek or volume are un-clickable. Also, the cpu usage of html5 h.264 videos seems at least as high as that of flash (unlike low cpu usage of VLC or mplayer). midori version that I used: --- Midori 0.2.4-a1a2510 WebKitGTK+ 1.2.0 (1.2.0) GTK+ 2.18.3 (2.18.3) Platform Linux i686 Identification Midori/0.2 (X11; Linux; U; en-us) WebKit/531.2+ google-chrome version that I used: --- Google Chrome 5.0.375.28 (Official Build 45883) dev WebKit 533.4 V8 2.1.10.11 User Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.28 Safari/533.4
Attachments
Add attachment proposed patch, testcase, etc.
Daniel Michalik
Comment 1 2010-05-03 07:50:20 PDT
I confirm this report using webkit 1.2.0 with midori 0.2.4 and epiphany 2.30.2: The html5 video plays fine but position and volume can not be adjusted anymore. I can not give any statement regarding cpu usage of the videos.
Bakhtiar Hasmanan
Comment 2 2011-01-27 21:34:33 PST
Confirmed this on Windows. With directsound/directshow audio out, sound won't returned when being enabled after muted and seek/scrub doesn't work too. Playback is fine though
Natalia
Comment 3 2014-03-05 05:21:45 PST
The issue is actual for QtWebkit based browser. It is simple to reproduce: open your browser(e.g. - fancybrowser from here: http://qt-project.org/doc/qt-4.8/webkit-fancybrowser.html)), load some html5 video - http://w3c-test.org/html/examples/elements/video/video01.html. The control for seek is un-clickable. The same for html5 audio. Also set position doesn't work for media element (<video>/<audio>) via currentTime attribute. Used environment: Fedora 19 (3.12.8-200.fc19.i686), Qt 5.2.0
Martin Robinson
Comment 4 2015-05-07 16:49:52 PDT
Can't seem to reproduce this in the latest.
Bakhtiar Hasmanan
Comment 5 2015-05-08 10:22:40 PDT
@mrobinson is there particular commit that fix it? AFAIK Win32 stuck at 1.x due to broken JSCore port in Webkit 2.x. Just in case backport is possible.
Martin Robinson
Comment 6 2015-05-08 11:03:33 PDT
(In reply to comment #5) > @mrobinson is there particular commit that fix it? AFAIK Win32 stuck at 1.x > due to broken JSCore port in Webkit 2.x. Just in case backport is possible. I'm not sure. This bug is so old and so many things have changed in WebKit. :/ perhaps we can get WebKit1 2.x working on Windows.
Note You need to log in before you can comment on or make changes to this bug.