faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Flash
by Kevin Krammer on Thursday 01/May/2008, @13:32
|
> Except the problem likely isn't in their code
judging by the issues that have already been fixed in the plugin, it is quite likely that most remaining issues are bugs in the plugin as well.
> If Adobe had a problem with Flash, it would be noticed by the countless users who use it every single day.
As we know it is noticed by countless uses who happen to not use Gecko.
E.g. one bug was that the plugin accessed GTK functions without calling gtk_init(), which only works if something else has already called that function.
Even a non GTK based Gecko engine would have failed that.
The fix was to properly call the init function, as documented in the GTK API docs.
A recent discovery is that the plugin calls a plugin host function and cannot handle user agent strings which include "like Gecko" but requires to have just "Gecko". However, any later call of that function can return the correct user agent, cleary indicating that there is a bug in the plugin code responsible for the first call.
> Clearly the nature of the problem is how Konqueror implements plugins.
Clearly the nature of the problem is how Adobe's Flasg plugin developers assume things outside the definition of the plugin API instead of properly using it an other APIs (see GTK misuse above)
> This is one of the many reasons I will never uses Konqueror as web browser.
I use Konqueror as my main web browser every single day, even with Adobe's Flash despite Adobe's best efforts to make this impossible.
It is awesome how Konqueror/KHTML/nspluginviewer developers manage to find workrounds and outside fixes for problems Adobe seems to be uncapable of fixing where they originate. |
|
|