![]()
Cool Mac Gear iPod Video iPod nano iPod 1G-2G iPod 3G iPod 4G iPod Mini PowerBook-iBook Garageband |
Flash Animations, QuickTime Movies and Java Applets seamlessly integrated into the rest of the content on a webpage or website has been the hallmark of the best web developers. But the coming version of MS Internet Explorer (in early 04) breaks that seamlessness by prompting the user before downloading each active content element (placed using object, embed, applet tags). This is a pain, but it’s not the first time MS did this to us. Remember having to replace
This is probably going to be the biggest hurdle web developers face in the coming months. So how can this be fixed? It can’t really, but it can be circumvented using JavaScript. You see, according to Microsoft, if you don’t put the code within the page or directly generate it while the page is loading it won’t trigger the prompt. So the solution is to extract the code to an external JavaScript file and call that code as a function. For example, find a web page that has an object tag like this:
Copy that code and create a javascript function with a unique name in an external file and paste it in a document:
Save the file with a .js extension Then replace the original set of tags with a link to the external javascript file and a function call
You have to do this for every page that has an object, embed or applet tag -- and that’s a lot of web pages. More information about this problem is available at Shameless Self Promotion I’ve written a piece of software that automates the fix for this. It is called IEWebFix. With a single click of a button IEWebFix scans the entire contents of a website and generates a list of files with offending codes. Then with another click the files are repaired. IEWebFix scans and repairs HTML, XHTML, XML, ASP, JSP, PHP, and CFM files. IEWebFix v 1.0 is available for immediate download from For more information, visit: By Ronald Northrip,
Page: 1 - 2 - 3 - 4 - 5
| |||||