Bug#644115: libwebkitgtk-1.0-0: fails to start YouTube videos, until user clicks outside the video area

Francesco Poli (wintermute) invernomuto at paranoici.org
Sun Oct 2 22:44:14 UTC 2011

Package: libwebkitgtk-1.0-0
Version: 1.4.2-2
Severity: normal

Hello, and thanks for maintaining WebKit in Debian!

I think I found a little issue with YouTube videos.
The issue is a bit annoying, but not a show-stopper at all.

When I load a YouTube page dedicated to a given video in
a web browser based on libwebkitgtk-1.0-0 (or on libwebkitgtk-3.0-0),
I see the rectangular area that's going to host the flash video and
the rest of the page, as expected.
Since I have the "set startStopped on" option in /etc/gnashpluginrc
(I use browser-plugin-gnash version 0.8.10~git20110618-3, I don't want
to install non-free packages...), the rectangular area just shows a
"Click to play" button. That's expected and it perfectly fits my tastes.
Once I click on the "Click to play" button, the area turns completely
black and nothing happens, until I click on the rest of the page,
somewhere outside the video rectangular area.
After that, the YouTube video player interface becomes visible and
everything works as intended (I can play/pause the video, set the
volume, and so forth...).

The fact that I need this extra-click outside the video area
is unexpected and most probably due to a bug.

I tested the following browsers:

/usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher needs the extra-click

midori (which depends on libwebkitgtk-1.0-0) also needs the extra-click

/usr/lib/webkitgtk-3.0-0/libexec/GtkLauncher needs the extra-click, too

epiphany-browser (which depends on libwebkitgtk-3.0-0) needs the
extra-click, as well

chromium (which is based on a modified version of WebKit, as far as I
understand) works fine, without the need of any extra-click

both galeon and iceweasel (which are not based on WebKit) work fine

In summary, it seems to me that this issue lies in WebKit, but not in
the modified WebKit used by chromium.

Thanks for your attention so far, I hope this bug may fixed easily.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libwebkitgtk-1.0-0 depends on:
ii  libatk1.0-0                      2.0.1-2     
ii  libc6                            2.13-21     
ii  libcairo2                        1.10.2-6.1  
ii  libenchant1c2a                   1.6.0-3     
ii  libfontconfig1                   2.8.0-3     
ii  libfreetype6                     2.4.6-2     
ii  libgail18                        2.24.4-3    
ii  libgdk-pixbuf2.0-0               2.24.0-1    
ii  libgeoclue0                      0.12.0-3+b1 
ii  libglib2.0-0                     2.28.6-1    
ii  libgstreamer-plugins-base0.10-0  0.10.35-1   
ii  libgstreamer0.10-0               0.10.35-1   
ii  libgtk2.0-0                      2.24.4-3    
ii  libicu44                         4.4.2-2     
ii  libjpeg8                         8c-2        
ii  libpango1.0-0                    1.28.4-3    
ii  libpng12-0                       1.2.46-3    
ii  libsoup2.4-1                     2.34.3-1    
ii  libsqlite3-0                     3.7.7-2     
ii  libstdc++6                       4.6.1-4     
ii  libwebkitgtk-1.0-common          1.4.2-2     
ii  libx11-6                         2:1.4.4-1   
ii  libxml2                          2.7.8.dfsg-4
ii  libxrender1                      1:0.9.6-2   
ii  libxslt1.1                       1.1.26-8    
ii  libxt6                           1:1.1.1-2   

libwebkitgtk-1.0-0 recommends no packages.

libwebkitgtk-1.0-0 suggests no packages.

-- no debconf information

More information about the Pkg-webkit-maintainers mailing list