This content has been marked as final. Show 12 replies
"Hobbis CoolBytes" <firstname.lastname@example.org> wrote in message
>I wonder if Macromedia have an offical response to this? Basically, all
> versions of Internet Explorer will disable the active x flash player!!!
Basically ... that is a gross exaggeration. It doesn't disable activex
controls at all. Flash Player etc will all still work in IE. Please read
up on the facts first before scaring everyone with such comments.
Ok, I'll tone down my comments a little with some facts: The flash player will still be able to play, but if the movie involves user interaction such as buttons etc, then the user is required to allow the movie to accept this interaction by clicking on the movie.
I think what I'm really after is Adobe's offical response to Microsoft's plans to implement the new feature in IE.
Basically .. if you don't make an appropriate change to your web page, then
if your visitor wants to click on your movie, they first have to click on
the movie (ie one extra click). Unfortunately, this also applies to other
mouse interaction (like followers etc). Also, if the movie is
non-interactive, then it still plays ok.
There are simple solutions already available with minimal addition to
existing HTML .. but I too am also am interested to hear what Adobe and
Apple recommend, and if that differs from what Microsoft recommend. I'm
sure there will be something soon.
Gross exaggeration? When your web sites (our four sites) are created with Flash menus, Flash players, Flash slideshows, Flash openings...NOTHING is an exaggeration! (easy for you to say) The MS IE changes have impacted virtually everything we have done. While the "simple solution" is helpful for those with plenty of time on their hands, it does require a LOT of extra work on dozens of pages. The sudden and unexpected changes by MS in how IE handles Flash was done with apparently no consideration for millions of people who use Flash. If I wanted a border around all my flash objects, I would have created one. I am irritated at this rather indifferent cavalier attitude to what is a major problem for many like us who are self-employed and create our own sites, but who are not cyber-geeks.
"BOSTONFLASHER" <email@example.com> wrote in message
> While the "simple solution" is helpful for those with
> plenty of time on their hands, it does require a LOT of extra work on
> dozens of
There is no solution that requires no work. Sorry .. that's jsut the way it
is. The simple solutions such as those at http://activecontent.blogspot.com
are going to be the best you can do re least work required. They only
involve adding three lines of tag to your existing web pages .. so its not a
BIG change. Yes .. it means work for you .. but that's just the way it is
and you'll have to put up with it.
> The sudden and unexpected changes by MS in how IE handles Flash was done
> with apparently no consideration for millions of people who use Flash.
It is not a change that just affects Flash .. it affects every activex
control that interacts with the user
> If I wanted a border around all my flash objects, I would have created
That's a very silly comment
> I am irritated at this rather indifferent cavalier attitude to what is a
> problem for many like us who are self-employed and create our own sites,
> who are not cyber-geeks.
That is why the simple solutions that require no changes to the existing
tags (just adding some simple pre-defined lines to existing HTML) are so
Jeckyl...Simple solution or not, your "so what-big deal" response to this is cavalier. I stand by my comment about a border around my Flash objects. You dismiss it as if it's nothing. It is not a silly comment...it's reality. I'm sure I'm not alone when I say I am busy and I don't want to waste time FIXING a problem created by someone else. Obviously I have no choice. Apparently some people have lots of play-time on their hands.
> Jeckyl...Simple solution or not, your "so what-big deal" response to this
I never made a 'what-big deal' response. Read my reply again.
I explained that it requires work from you as a web developer to ensure your
site works seamlessly with Internet Explorer (as it now is). My response
was, rather, a 'whether you like it or not' response .. and that's simply
how it is.
> I stand by my comment about a border around my Flash objects.
You mean your flippant remark about adding them yourself if you wanted it?
That simply shows your complete ignorance of the issue. The change was not
so you would have an automatic border around activex objects .. that's not
the point of it, its just a side-effect of the change required to prevent IE
infringing the stupid EOLAS patent.
> You dismiss it as if it's nothing.
No .. YOU were dismissing it as nothing (or almsot monthing) .. as just a
border around your control. Its a much bigger issue than such a
trivialising remark suggests.
> It is not a silly comment...it's reality.
Indeed .. and you under-stated the nature of the reality of the effects of
the change. Obviosuly you don't see it as big a deal as it really is.
> I'm sure I'm not alone when I say I am busy and I don't want to waste time
> a problem created by someone else. Obviously I have no choice.
Exactly .. NOONE wants to have been placed in this situation. NOONE is
happy about it (least of all Microsoft).
So now you have to do some work to remove the border you don't want. Tough
.. complaining about how you don't like it isn't at all helpful.
> Apparently some people have lots of play-time on their hands.
No .. we are all in the same boat .. we just don't make flippant remarks
And .. despite your attitude, I will give you the link to a page that lists
the simple solutions as well as links to the more complex 'official'
I love reading this thread!
Meanwhile, I have made a work around and it is used on this site:
It wasn't that hard to work around it didn't take much time to implement.
BOSTONFLASHER I can fully understand your fustration on this matter but it's not really Microsoft's fault. Someone took them to court over and they (Microsoft) lost so now they have to do it this way.
I'm in the same position as BOSTONFLASHER, but it seems that we just have to deal with it. I already posted about this annoying problem 2 months ago and they replied me:
What do we do? We sit back and enjoy the quieter, less annoying web. ;o)
that's the attitude we all want!
> i guess what bostonflasher was asking is: rather than telling everybody to
> 35 in
> one page (a page with flash content using tables, to avoid using old
> frame-style pages), make it already FIXED from inside the authoring
It is if you get the update from Adobe
> that is, as all we know, Flash 8 exports HTML, the big question is,
> WHY DOES THAT HTML DOESN'T EXPORTS THE HTML WITH
It does when you get the patch from Adobe .. or rather, it will fix the html
code for you
The other techniques are more for fixing existing pages, or if you do your
own HTML coding (ie don't just use the plain vanilla swf-only html that