The player throws a javascript error in IE8 when the remote playlist feature is used. Not only is an error showing on every page it appears on a problem in itself, it also makes calls using the remote playlist functionality via javascript almost impossible, although connecting two players still seems to work (albeit with an error).

The error caused is in "function __flash__addCallback" ie flash side and is an "object doesn't support this property or method error". Delving deeper the error seems to be caused by methods being named 'play' and 'stop'. Altering these names slightly removes the error and restores functionality. http://digitarald.de/forums/topic.php?id=315 is an example of someone else having experienced this. Alternatively check out your own demo page in IE8 with debugging switched on.

CommentFileSizeAuthor
#7 dashPlayer_v135-beta3.swf_.zip56.91 KBscottalan
#4 dashPlayer_v135-beta2.swf_.zip56.92 KBscottalan

Comments

tony-b’s picture

tony-b commented

Just a small addition. I mentioned connecting Dash players isn't a problem...well even then it is if you're trying to connect a playbar remotely. Also seems the list of problematic method names extends beyond just 'play' and 'stop' and at the very least includes tags, item and length too (although not currently used in Dash it seems). Needless to say pre-pending all addCallback names is probably the safest resolution.

scottalan’s picture

scottalan commented
Status: Active » Postponed (maintainer needs more info)

Your post has been noted and we will look into the situation.

-Scott

tony-b’s picture

tony-b commented

Thanks Scott - the fix itself should be easy as it really is just a naming convention thing and Microsoft not really thinking through their own use. As I say though, considering the number of people using IE8 now it really is quite an issue.

scottalan’s picture

scottalan commented
StatusFileSize
new dashPlayer_v135-beta2.swf_.zip56.92 KB

Replace your player.swf with the one below and let me know if this corrects the problem. I'm having trouble with my IE8 in Parallels so I was unable to check it for myself. Travis and I looked into it and I made the 'naming' adjustments. Let me know of the outcome, I would definitely appreciate it.

Content Template Body:

$params['api'] = 3;

dashconfig.xml:

<flashvars>
<api>3</api>
</flashvars>

-Scott

tony-b’s picture

tony-b commented

Many thanks for the speedy responses Scott. Initial trial has a couple of problems...

If the default skin is used by leaving the skin field blank, an error is returned:

[IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2036: Load Never Completed. URL: http://******.com/sites/default/files/skins//skin.swf"]

(obviously the *'s are a replacement for this post) so it seems like the file is no longer adding the 'default' part of the path if this is left blank. Not a huge issue my end as we're going to skin but could be a problem for many if they don't declare a skin.

Related to the initial problem the error still occurs in JScript line 48 where "play" is still being used somewhere it seems. Obviously this end I can't say for sure where and it appears you've certainly removed most if not all of the methods and functions labeled play. Firefox still works fine - it's just the ie8 problem still.

There's also a small problem now with the amfphp/services side of things that wasn't there before. Views are loading fine but if you try to load a node ie '$params['node'] = 94;', you get the error:

Access denied
AMFPHP_RUNTIME_ERROR
/home/***/******/sites/all/modules/amfphp/amfphp.module

in the flash player debug log. This was fine before the change and I've treble checked all the module/config settings to make sure nothing has changed my end.

I'll continue to play about this end too and if I come across anything helpful I'll get back to you.

tony-b’s picture

tony-b commented

Quick update - the AMFPHP and default skin problem are related I believe. I had keys disabled whilst setting up and so no key entered. If I enable keys for services the problem with AMFPHP goes away, so I'm guessing it's currently not dealing well with any blank fields in the config be it skin or AMF.

Still have the problem with function/method names somewhere though and the original IE8 error.

scottalan’s picture

scottalan commented
StatusFileSize
new dashPlayer_v135-beta3.swf_.zip56.91 KB

To All----


Updated Version:

* IE8 compatible (so far...)
* CallBack names were apparently reserved words...

* If you are using this with Services < 0.15, then you will use:

$params['api'] =1;

* If you are using this with Services = 0.15, then you will use:

$params['api'] =2;

* If you are using this with Services 6.x-2.0, then you will use:

$params['api'] =3;

-Scott

scottalan’s picture

scottalan commented
Status: Postponed (maintainer needs more info) » Fixed

-scott

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.