Hello,
I have a site: www.class-e-ads.com of which the home page has a set of 3 ScriptyFader boxes set to change every 12 seconds upon load. Also, in the same area is a Easy Web Animator QT.mov positioned in Scripty Lightbox2 w/ Transition FX set to show ‘hidden’ for duration 5, delay 6. The fader boxes are in front of the QT.mov in CSS positioning.
When viewed with FW5P viewer the result is pretty much as desired, as well with Safari 5.0.5 locally and on line (cache cleared between loads).
Things start breaking down with Google Chrome 11.0.696.77, in that the initial page load is fine but after the FX delay a QT black screen/Logo pops up for a varying amount of time (no fade up), then the QT.mov plays, but on top of the ScriptyFader rotation (it is under the movie, I can cause them to highlight with the cursor). I would like to keep the entities separate, but if Chrome can not be made to behave as Safari does I could put everything in the QT.mov.
In FireFox 4.0.1 with an emptied cache, the page load is OK, but the QT.mov pops right up without fade-up and with the wrong timing, THEN does/will not load again until cache has been dumped again (just the QT.mov that is). FF has been a real pain for me so I had dumped it and reinstalled. Now I have not any extensions and only an assortment of 14 media type plugins in the add ons.
I hope this is clear, and thank anyone in advance for your advice, as always.
It is very difficult to animate a plug-in like QuickTime or Flash, or
to make all browsers respect any layering decisions you have made in
your page in conjunction with that content. The best way to think of
this is as though the QuickTime plug-in used a cookie cutter to chop a
hole through the page wherever you place the movie – through all
layers from the top of the stack all the way down to the bottom.
Anything else that falls within that rectangle is basically gone.
There are tricks to work around this, but they are not universally
honored by various browsers. You can either spend your life applying
hack upon hack, or you can design around the problem.
Walter
On Jun 18, 2011, at 4:22 AM, Frank H wrote:
Things start breaking down with Google Chrome 11.0.696.77, in that
the initial page load is fine but after the FX delay a QT black
screen/Logo pops up for a varying amount of time (no fade up), then
the QT.mov plays, but on top of the ScriptyFader rotation (it is
under the movie, I can cause them to highlight with the cursor). I
would like to keep the entities separate, but if Chrome can not be
made to behave as Safari does I could put everything in the QT.mov.
I gather your suggesting that where media such as these are, media such as these are only- I should incorporate the fader items into the animation.
Thanks again
Frank H.
On Jun 18, 2011, at 6:33 AM, Walter Lee Davis wrote:
It is very difficult to animate a plug-in like QuickTime or Flash, or to make all browsers respect any layering decisions you have made in your page in conjunction with that content. The best way to think of this is as though the QuickTime plug-in used a cookie cutter to chop a hole through the page wherever you place the movie – through all layers from the top of the stack all the way down to the bottom. Anything else that falls within that rectangle is basically gone. There are tricks to work around this, but they are not universally honored by various browsers. You can either spend your life applying hack upon hack, or you can design around the problem.
Walter
On Jun 18, 2011, at 4:22 AM, Frank H wrote:
Things start breaking down with Google Chrome 11.0.696.77, in that the initial page load is fine but after the FX delay a QT black screen/Logo pops up for a varying amount of time (no fade up), then the QT.mov plays, but on top of the ScriptyFader rotation (it is under the movie, I can cause them to highlight with the cursor). I would like to keep the entities separate, but if Chrome can not be made to behave as Safari does I could put everything in the QT.mov.