Skip to Site Navigation | Skip to Content

Blog

No more "Click to Activate"

For almost two years now, web developers and the general browsing public have felt the pain of the "Click to activate" barrier to multimedia content when using Microsoft's Internet Explorer browser. Yesterday, Microsoft announced via the IEBlog that the patent issues have been resolved and a licensing agreement is in place that will allow Microsoft to remove the restriction from the browser. 

For those of you who are not familiar with the case, Eolas brought a suit against Microsoft in 1999 claiming the company's web browser violated their patent concerning embedded media in hyperlinked documents. As a result of the judgement against them, Microsoft altered the behavior of the browser to display any Active X media content in web pages as inactive until the user manually "activated" it via the infamous "Click to activate" user interface element. The update was released in early 2006 and affects both Internet Explorer 6 and 7 versions, including the current version in Microsoft's Vista operating system. This new behavior was pushed via the Windows Update system as an automatic update. Many users simply woke up one day to their browser behaving strangely.

From a user experience standpoint this was a nightmare. From the point of view of web developer it became even worse as we spent several months following the update answering client questions and publishing changes to accommodate customers who didn't understand why their beautiful Flash movie suddenly "didn't work." Numerous workarounds were devised and implemented into nearly every developer's workflow worldwide. Despite the perceived shortcomings of the world's most-used web browser, it could not be ignored.

So, you'd think we'd be excited to see this finally resolved and removed from the browsers—and don't get me wrong—we are. But the fix is inexplicably not to be released until April 2008 and the whole issue shows just how big an impact a silly decision like this can make. Microsoft can't make users accept their update no more than they can make them upgrade to IE7, currently about half of the IE browser share. This is desktop software. Microsoft can't take it back. There is no "undo". This is a permanent part of the web now. So Microsoft can release a patch and wipe their hands clean while developers are stuck supporting the effects of this behavior for years to come. It is unfortunate to think that a dispute between two commercial entities can have such a profound impact on the functionality and history of the web over such a petty issue.

9 comments (Add your own)

1. Terry Apodaca wrote:
This is indeed a good thing for those IE users...and there's nothing wrong with that as long as MS continues to try and move towards a more open and standards based browser. I am a MS developer by day so I have to deal with IE all the time...and this "CLick to activate..." sure has been a pain. I know there are workarounds, and we tried a few...that ended up being more buggy than worth supporting. Anyone have any links to some good fix/workaround until April comes?

Mon, November 12, 2007 @ 11:00 AM

2. Jason Zimdars wrote:
Terry, for Flash it's easy. Geoff Stearn's fantastic SWFObject is the best choice. It is lightweight, works in all major browsers and is actually so feature-rich as to be the best way to embed Adobe Flash content regardless of browser. I was using it before the Eolas issue and will continue to use it after it is gone. However, when it comes to other other media and Active X content, there isn't a clear favorite. I have to admit with the prominence of Flash video we rarely use any other format, but when we do, a simple document.write script to place the embed tags via script works for these media types as well.

Mon, November 12, 2007 @ 8:30 PM

3. internet marketing wrote:
Yes, it is INDEED a wonderful information for all IE users.

Mon, November 12, 2007 @ 11:52 PM

4. Terry Apodaca wrote:
Thanks for the info Jason! I've used SWFObject for most of (we don't use much) our flash content. We are also mixing a ton of classic asp with ASP.NET so it's hard to keep up with what works best with them...so I try to stay away from as much activeX content as I can...but when I have to use it with old controls, I've seen this: http://www.amarasoftware.com/flash-problem.htm Used it with success and without...so it'll be a major relieve when that date rolls around! As for a simple document.write, I mostly do what others do: var activeContent = ' ' + ' '+ ' '+ ' '; document.write(activeContent); Or some variation of the above.

Tue, November 13, 2007 @ 8:01 PM

5. Terry Apodaca wrote:
Oooops, there was code between those quotes...but I am sure most that read this blog get the gist of it.

Tue, November 13, 2007 @ 8:02 PM

6. Jason Zimdars wrote:
Thanks for posting that code tip, Terry. That's very much like what we're doing for any non-Flash media content. I'm sure others will find that helpful.

Wed, November 14, 2007 @ 4:16 PM

7. Nickolas wrote:
Glad the change is going to take place. I've been hasseling with this issue for some time now. Can't wait to get rid of the "Script" fix.

Thu, November 15, 2007 @ 12:24 AM

8. moreclick wrote:
it is great article thanks for sharing.

Sat, March 6, 2010 @ 5:12 AM

9. HooperMarion wrote:

Wed, June 23, 2010 @ 6:08 PM

Add a New Comment

Enter the code you see below:
code
 

Comment Guidelines: No HTML is allowed. Off-topic or inappropriate comments will be edited or deleted. Thanks.