bin20060407 / swfobject

Automatically exported from code.google.com/p/swfobject
0 stars 0 forks source link

SwfObject in Spotify Desktop Client Webkit #631

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Apologies if this is the wrong place for this post - just looking for some help.

What steps will reproduce the problem?

1. We are building a Spotify Ad in the spotify client (web kit browser within 
Spotify Desktop Client). When using SwfObject 2.2 and Flash 11+ we see a white 
box and no flash is loaded.

2. If we use an earlier version of Flash (eg. 10.2), it runs fine.

3. Also if we run in a regular browser with the same set up everything works.

Could anybody point me in the right direction for pinpointing the issue - does 
the white box give us any clues??

Thanks in advance.

Original issue reported on code.google.com by i...@kerve.co.uk on 22 May 2012 at 8:39

GoogleCodeExporter commented 9 years ago
Unless you are testing the client under OSX, it should be Trident not Webkit.
Please provide O/S and version of IE or OSX.

Original comment by jhiswin on 1 Jun 2012 at 9:23

GoogleCodeExporter commented 9 years ago
The issue is that Adobe have split the plugin executables for Windows machines 
to Internet Explorer and "other browsers" as separate downloads. Spotify uses 
Webkit as it's browser rendering engine in ad pages, however the way Spotify 
looks to see if you have the correct Flash plugin is by monitoring your default 
browser that was first installed. In most cases on Windows this is Internet 
Explorer.

So because it's checking Internet Explorer the flash plugin, it will find it 
but as that Flash plugin is ONLY compatible with Internet Explorer and NOT 
WebKit you'll see the white box issue.

We spent a considerable amount of time debugging this to find a solution 
however unless Adobe creates a generic installer for all browsers on Windows, 
or Spotify rebuild their browser setup to be standalone and not use plugins 
from your default browser there is no solution at present.

Unless someone has found a way round this?

Original comment by benjibar...@gmail.com on 2 Jun 2012 at 9:52