vurnews.blogg.se - Javascript flash player detection

The new detection doesn’t even come close to validating.

It’s not valid HTML or XHTML – Valid XHTML documents aren’t for everyone, but when you have clients specifically asking for them it’s nice to be able to deliver.

This is a hassle to edit if you need to make changes, and makes it very tough for designers who don’t know Javascript to go in and modify attributes.

Tough to modify the code – It suffers from the same drawbacks as most Javascript embed techniques – placing tons of Javascript document.write() calls and writing out your object or embed tags to the page.

Also: what happens if you need to upgrade the Javascript for some reason? While the code should be very futureproof, you never know when a bug might pop up, and you’ll be stuck editing all of your HTML files that have Flash movies included in them.

I’m not sure why they decided to leave in the VBScript when there are other reliable ways to create and test for ActiveX objects. Inline Javascript code (and lots of it) – Who wants to copy a bunch of Javascript and VBscript onto every single page that uses Flash? While it might be possible to move the Javascript into an external file, you would still have a small amount of VBScript on each page (or another external file to include).While it’s a good first try, it is greatly lacking in a few basic needs of most web developers. It’s no wonder then, that the latest version uses Javascript as the suggested detection method. The detection kit has has been around for the last few versions of Flash, and usually changes with each version to include whatever the latest trends in Flash detection are. With the announcement of Flash 8 today, Macromedia also quietly pushed out their new detection kit.