thanks.. you answered it perfectly..
On Oct 27, 3:29 pm, "Getify Solutions" <[EMAIL PROTECTED]> wrote:
> 1) "ExpressInstall" content (the SWF) will replace your alternate content,
> if it is able to run. This means that the user must have already at least
> FP6.0.65 (where Adobe introduced EI). If they Flash but less than that, the
> alternate content will display and no EI will be triggered.
>
> 2) For EI to run, JS is required, as is FP6.0.65+. "AdBlock" aside, if the
> user has those two things, and you specify a version greater than what they
> have, they will see EI. Otherwise, they will not see it, and will instead
> see the alternate content. This goes for static publishing as well as
> dynamic publishing, AFAIK.
>
> --Kyle
>
> --------------------------------------------------
> From: "swfster" <[EMAIL PROTECTED]>
> Sent: Monday, October 27, 2008 4:21 PM
> To: "SWFObject" <[email protected]>
> Subject: Re: force download of Flash Player 10 on Mac platform only
>
>
>
> > fyi, i already tried, opaque and a thousand other iterations to fix
> > this before upgrading flash to fix it.
>
> > it's a known bug in ff mac. the only fix is to upgrade.
>
> > i somewhat disagree with your assertion to force others to update if
> > they don't need to.
>
> > painless is a relative term. some are likely to ditch the site if
> > they see the upgrade message popup.
> > and there is zero *functionality* in flash player 10 required to run
> > my swf. it's purely a rendering issue
> > in a *single* browser platform that was not accounted for when they
> > built a prior version and only somehow related to mac
> > ff v 3.0.3 ppc. it works with lower versions in every other browser /
> > platform combination.
>
> > finally, it's not necessarily my job to force adobe's security issue
> > fixes on others. would it be better
> > for the community sure. is that my responsibility? well, due to the
> > nature of the way adobe distributes
> > it's flash player, unfortunately yes - either web developers force the
> > upgrade via utilities like swfobject, users
> > download a new browser that may force the issue or users somehow go
> > and get it themselves (not likely).
> > not trying to bust your xxx, i just like to have options and applying
> > the update for those that do NOT need
> > it seems like using a sledgehammer where a toy hammer would be better.
>
> > i really appreciate the js suggestion.. a wrapper function would
> > probably be the way to go. in this case,
> > the work involved to make that work might mean actually forcing fp 10
> > on everybody via swfobject
> > might turn out being the toy hammer :-)..
>
> > quick followup. i'm used to using swfobject 1.5 and i've never used
> > the force download feature (which i believe is
> > called 'express download'). i DO use the default div content
> > technique (if flash player is absent / or disabled, then
> > it displays the content of target swfobject div).
>
> > questions:
>
> > 1) if i use swfobject 2.0, and if a express download is enabled, but
> > the user doesn't have the right version,
> > will they see the default swf replacement content AND the express
> > download instructions (overlayed over the
> > default replacement content) or ONLY the express download instructions
> > (e.g. takes the place of the default
> > replacement content)?
>
> > 2) if they don't have flash installed at all or disabled (not an
> > existing wrong version), will the express download message
> > display or the replacement content? I would think if i'm using a
> > browser plugin like flash block, the replacement
> > content will show and i will not be prompted with express install.
> > however, if for some reason someone didn't have the
> > ANY flash player installed, i imagine that will trigger an express
> > install right?
>
> > thanks
>
> > if anybody else wanders here and has a sample version / platform js
> > wrapper for swfobject, i'd be mighty
> > glad if you post
>
> > On Oct 27, 6:58 am, "Getify Solutions, Inc." <[EMAIL PROTECTED]> wrote:
> >> There are PLENTY of security reasons why ALL users should upgrade to the
> >> latest Flash Player. At the very least, 9.0.124, and really, 10.0.12.36.
> >> I
> >> think you should just have all users upgrade (very painless for them, if
> >> using swfobject's express-install) just for the betterment of the general
> >> web community.
>
> >> The better thing to try might be to actually trouble-shoot the problem
> >> rather than trying to avoid it. You might look at and possibly switch
> >> from
> >> "wmode:transparent" to "wmode:opaque" for your SWF embedding, as opaque
> >> seems to be more stable cross-browser (transparent is *really* buggy).
>
> >> ---------------------
> >> SWFObject's API doesn't support platform-dependent version checking. You
> >> could of course roll your own solution wrapped around the calls to the
> >> SWFObject API... it involves checking the navigator.useragent string. In
> >> general, this is *not* particularly easy, with all the different browser
> >> variations, but with making such a specific targeting scheme, you ought
> >> to
> >> be able to figure out exactly what identifies your problem browser.
> >> You'll
> >> have to run test scripts in several different test environments to
> >> guarantee
> >> which parts of that user-agent string are unique only to the browser
> >> you're
> >> targeting.
>
> >> But if you can definitively figure that out, you can conditionally test
> >> for
> >> a browser in the loading of your page and pass a different version to
> >> SWFObject's createSWF() (or registerObject()) function based on that
> >> check.
>
> >> --Kyle
>
> >> --------------------------------------------------
> >> From: "swfster" <[EMAIL PROTECTED]>
> >> Sent: Monday, October 27, 2008 12:19 AM
> >> To: "SWFObject" <[email protected]>
> >> Subject: force download of Flash Player 10 on Mac platform only
>
> >> > i have a site where dropdown menus overlay a swf on the front page.
>
> >> > this combination works fine using flash player 9 in every browser and
> >> > platform known to man with the exception of Firefox 3.0.3 MAC (on a
> >> > power pc platform). basically i get a bunch of screen flicker when
> >> > the drop down menu overlays the swf on FF mac w/ flash player 9.
>
> >> > If i upgrade flash player 9 to flash player 10 on the power pc mac,
> >> > the flicker problem goes away.
>
> >> > here's my dilemma. i'd like to use swfobject 2. but i only want it
> >> > to force mac users (preferably mac ppc architecture only) to download
> >> > flash player 10. 90+% of other site visitors are on NON MAC
> >> > platforms. they shouldn't be forced to download flash player 10 if
> >> > they don't need it.
>
> >> > is there a way to make swfobject ONLY force a player 10 download on
> >> > MAC detection ONLY and leave PC users at their current player
> >> > versions? if so, can someone point me to the right parameters or an
> >> > example to do this?
>
> >> > thanks much!
>
> >> > fwiw, if i could specify MAC ONLY + Firefox 3.0.3 ONLY + PPC ONLY that
> >> > would be even better. But mac only is sufficient if that's all that's
> >> > available.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SWFObject" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/swfobject?hl=en
-~----------~----~----~----~------~----~------~--~---
