anyone whos bored - please check:
http://www.jgrant.com/lionshare/brand.htm
in IE - the slideshow images fade in and out
in FF - they click / click / click
i can live with that - but there is a speed issue:
in order for FF to go the correct speed i want - ie has to be slowed down to an almost "dont even notice theres a slide show" delay
actually - here's a link of just the include:
http://www.jgrant.com/lionshare/slides_brand.htm
when i set the speed in ie to be like ff - ff goes insane at like 2 pic a second clk,clk,clk fast
ive searched and cant find any other fading scripts that work in both
any help would be appriciated - otherwise ignore ![]()
-
-
This is probably not what you are looking for, but can you just have two methods based on the browser type
?
-
Hi Jamie,
Do you use MozOpacity for Firefox?
object.style.MozOpacity=op;
//where op is a decimal between 0 and 1.
-
-
bsilby wrote:
Hi Jamie,
Do you use MozOpacity for Firefox?
object.style.MozOpacity=op;
//where op is a decimal between 0 and 1.
So you're reccomending using a non-standard feature.
For a browser touted for its great standards support.
As a workaround for a browser-specific standard code rendering problem. -
NeoTOM wrote:

bsilby wrote: Hi Jamie,
Do you use MozOpacity for Firefox?
object.style.MozOpacity=op;
//where op is a decimal between 0 and 1.
So you're reccomending using a non-standard feature.
For a browser touted for its great standards support.
As a workaround for a browser-specific standard code rendering problem.
No, he was asking a question. Read it again.
-
NeoTOM wrote:
So you're reccomending using a non-standard feature.
For a browser touted for its great standards support.
As a workaround for a browser-specific standard code rendering problem.
I'd recommend using the non-standard feature if it gets around the problem and makes the page look right. Its quicker than waiting for the Moz team to fix the bug. -
bsilby wrote:
I'd recommend using the non-standard feature if it gets around the problem and makes the page look right. Its quicker than waiting for the Moz team to fix the bug.
Cue W0bbo
-
Opera 8 and Firefox (as of 1.0.4) both support the Opacity: <decimal>; value. Rather than the propriety "-moz-opacity: <decimal>;" property.
-
I think the reason that FireFox goes Spaz on the timing issue is cos there is no fading in Firefox, whereas there is in IE. So the time that it takes to fade in IE is removed when viewing in Firefox, making it run like crazy between the pics.
But I think w3bbo's right, you can use the standard opacity property now that it's supported in FF.
Just my two cents
-
I would just use an animated GIF image myself ^Shrug^
Could even create it server side on the fly. -
so from what i can tell its a ff bug and the best way to go is to separate the script - per browser
unfortunately i dont know how to program - so inserting a detect browser script within and exisitng script is beyond me
if theres an easy way to do this id love to use it
<script
if ff = same script (using existing time)
if IE = same script - i can speed it up
/script>
?
-
Manip wrote:I would just use an animated GIF image myself ^Shrug^
Could even create it server side on the fly.
GIF doesn't support alpha-channel opacity.
Whilst MNG does (Animated version of PNG), support was removed from Firefox a while ago.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.