A couple of years ago Internet Explorer cause millions of programmers and users alike a giant pain by making users click on a flash object, ActiveX object, and java applet before the object became active and usable. Businesses, of course, cried out for their programmers to fix the problem and programmers pulled their hair out for weeks. As one of those programmers, I can tell you that businesses wont take "Microsoft screwed things up" for an answer and luckily I found a solution that works without requiring that the user do anything.
The solutions requires the use a small JavaScript file strategically placed immediately after the Flash object's </object> tag.
That's all you have to do. The JavaScript code grabs the object and sets the object's outerHTML equal to itself, thus nullifying IE's effort to annoy the user.
I spent a few months experimenting with different approaches for writing simple, elegant and maintainable media queries with Sass. Each solution had something that I really liked, but I couldn't find one that covered everything I needed to do, so I ventured into creating my...
One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating:
new Element Madness
The first way to create UI-driven...
As I continue to learn jQuery, I think it's important that I begin by porting over scripts I've created using MooTools. One of those scripts is my Color Palette Generator script, which debuted on Eric Wendelin's blog. For those of you that...
These directions are not clear for a non-programmer. Can you help me? I’m using Dreamweaver 8.
Wow that code fixed my problem. Thank you so much!
hi, i was trying to solve this problem, and i couldn’t download the flash-fix script… would you please upload it again? thx
I was a little confused by this. What is the code and where to I place it exactly?