I had to shout out loud on this one, though ZDNET also wrote a nice article about it. Believe it or not, IE's latest update (went through roughly 10 days ago) has created havoc on the web, for both web designers and end-users. As I type, anyone using Internet Explorer now has to "activate" any flash or active-x element related to their website (EOLAS 521 millions lawsuit anyone?). This means that accessibility wise, our industry is now suffering greatly. Microsoft is very displeased with the decision (duh!) although they probably saw it coming a century ago.
For my part, I'm kinda concerned that very little discussions have been made about this tremendous blow to web design in general. I mean, do I need to call all of my customers which I managed their websites (like 60++) and tell them: "you know, there was that patch because of that lawsuit against Microsoft, and since you use Flash/active elements, it would cost you X$ for the quick fix". I mean, things like that happen, but I hate the fact that most of the "non-tekkie" users are the ones on the line. We can switch easily to other browsers, and some web designers will do it for their customers, but many won't and even with IE7 out, some will still have IE6. Most of my friends and customers I've been talking to recently were somehow annoyed in the last 2 weeks, having to double-click any flash element on any site they surf or visit. What does this all means? It means Microsoft got caught using someone else "free but don't commercialize please" technology, and it means the end-user (again) is paying for that.
If you are still using IE for browsing and want to avoid the double-click for active elements, consider Firefox and do share your thoughts on this ridiculous accessibility issue.
p.s. I made this post in French, too for anyone who's interested.
(edited by Rand --> thanks, and by the way, flag my major English flaws!)
May they reach the lowest low possible. DHTML and Voken type banners are simply killing the banner industry.
As for flash concerns, Flash is an awesome language, it is just overly misused by most of web designers, and this is due to the early ages of "flash is everything" + the fact that customers got the idea that "flash is everything" because they see way too much Hollywood movies. Flash should support a website and attract the eyes for a call to action or to do awesome stuff on website.
Guillaume,
Thanks for the heads up on the cause this at SES. I've forward them a solution. Of course I warned this client many times (they're a agency) of designing client web sites in 100% Flash. Best part their stle is to start with a black screen.
So their clients saw a big black box where the sites should be.
While many consider me a Flash hater I also go back about 8-9 years to a keynote by a VP at Macormedia on the top 10 reasons not to use Flash. Great talk of course 1/2 way through it, it switched to why use Flash. If people would have listen then, their sites would be fine now.
This issues is going to hurt Adobe/Macromedia as much as it is going to hurt Microsoft so expect an easy fix really soon. Because we all know that typical users (except kids and geeks) won't hunt for a solution they'll just assume the site is broken.
People still use Flash? I thought it died with html frames.
I had dreamed it would at least block the pop up flash ads. It even worse... takes two click on the 2pixel "x" to close them now :'(
The best way to fix the issue on your sites: embed your flash object using Flashobject.
This is a way to get your code to validate AND overcome the IE6 click issue.
For all the flash haters out there - I get your point, but don't blame the technology for its misuse. I've seen some amazing implementation of flash that works very well when done by a competent team.
Technically this affects firefox and other browsers too, it's just that EOLAS only sued MS. If they decide to sue other browsers as well, expect them to have to remove functionality too.
We had some discussions on it at Cre8asite when it happened (the initial loss of the case happened a year or 2 ago...) but it got relatively ignored until jsut before the patches were to go out.
It's annoying, but if MS had the patent, I'm sure they would've sued Opera/Firefox etc for using it anyway.... So I don't mind them being bit in the butt a bit....
I think it's great and anyone involved in SEO should think it's great too. Since when has Flash or Active objects been "accessible" to anyone? Last time I looked at a Flash website in my text browser I would amazed at how short (and useless) the page was.
Haha Aaron! And yes Rand, this is the real question. Although my team just came back from Flash in The Can (FTIC) in Toronto and they were talking about a flash-based shopping cart that you could be dropping the product in the basket "virtually" like MAC easy to use OS system, I think there is more thinking to put into that for the years to come, as Flash won't die...
Anyway: from what my team has heard... the future in that industry is "Flex", a new and upcoming rich media product by Macromedia.
Also heard that IE 7 should put an end to the double-click issue and make it a one-time event, so that future interactions will be seemless once you activate one Flash control.
This reminds me of something I found the other day that had Kat and I in stitches.
firefoxflicks - wheee!
i too forgot about the update and went to my IT guy as i knew he updated the secruity in the building..
It was a bit annoying as i was just putting the finishing touches to a flash based navagation for a client, but i went back and fixed the whole site so it works in IE before launch at no extra cost to them. They were more than happy.
I havent tested but i have heard that the latest beta of IE7 already has the Flash patch installed, i would interested to know who the final release will teach Flash.
I think the real question is - what does this do for the future of active elements like Flash? Are we going to see less CTR on the elements? Will it be even less valuable to use Flash in websites?
I admit being totally ignorant/forgetful and thought it was my new computer or something I'd installed (security-wise, etc) that was causing the damn double-clicking... Thanks for the heads-up.