[rekonq] Re: anyone else having problems with rekonq and Flash?
adjam7 at gmail.com
Thu Dec 30 11:07:48 CET 2010
On Wednesday 29 December 2010 22:00:31 Alexander van Loon wrote:
> Today I migrated to Kubuntu 10.10 on my desktop, after having used that
> distribution for a few months on my notebook already. Now that I’m using
> KDE and Rekonq full time I noticed that there are some problems with Flash
> (the 64-bit beta in my case to be precise). I suspect that those problems
> are not related to Flash itself, but rather KDE’s implementation of
> Please see https://bugs.kde.org/show_bug.cgi?id=261523 for a description of
> my problems. There are other bugs related to Flash on KDE’s Bugzilla -
> https://bugs.kde.org/buglist.cgi?quicksearch=rekonq+flash - but none with
> any comment from a developer. I searched through the archives of this
> mailing list for the last few months, but Flash isn’t mentioned there
> either. Google didn’t tell me anything either, except for relatively old
> forum posts, which I considered no longer relevant. I expected to read
> that other people would be affected by this problem as well, because Flash
> is unfortunately so important. Are there any other people experiencing
> problems, and are there any known solutions?
> rekonq mailing list
> rekonq at kde.org
I hope I can reply here to your question explaining all the problems "flash"
related we can meet surfing the net with the KDE browsers.
First of all, flash itself. I have no experience with flash 64 bit, but I
usually hear complains about the differences from 32 to 64 bits in (some)
precompiled software. Here, we obviously cannot do nothing but compare flash
performance and behavior viewing the same site eg with rekonq and with firefox.
As example, I noticed from when I upgraded my X11 that flash no more properly
support fullscreen view, so that every time it stops to load/cache new
content, fullscreen automatically switchs off :(
Second, nspluginwrapper. This is a nice piece of code from KDE, that can load
in another process some plugins (eg: flash) and that can be embedded in
KHTML uses it, so all problems flash related in KHTML are from that part of
code. I suspect it is unmaintained or anyway it is not in active development,
but in maintenance mode.
KWebkitPart relies on QtWebKit flash support in the same way rekonq does.
At least... rekonq relies on QtWebKit flash support for sure, while
kwebkitpart... did the last time I checked cause of some bugs on the
So, let's talk now about rekonq. Flash management depends on 2 components:
QtWebKit rendering and network integration. You may probably know that, while
QtWebKit network layer has been implemented via the QtNetwork libs (QNAM and
friends), KDEWebKit relies on KIO to do it. KIO is KDE network layer, that
basically provides the full KDE integration (network settings, proxy, easier
kpart support, etc... basically what let us be a KDE browser).
On this side there is a problem in kio_http integration with WebKit that
you'll find hopefully fixed in KDE SC 4.6 RC2 (surely for 4.6 final).
On WebKit side, I can just say I don't wish anyone to work on flash support...
:) but I know someone does it and he is doing a great work!
Hope this helps.
Andrea Diamantini, adjam
GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F
IRC: rekonq at freenode
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rekonq