since it's the entire site
Good point. But that's why it's hard to help you because few of us
have time to sort through your entire website :P
Most of the time you can pinpoint the problem simply through the
exercise of separating the code into a simple test.
At the very least you can post the code you used to create the
effect. I did manage to find it:
var myFxa1 = new Fx.Tween(document.id('demo-inner', {
duration: 'long',
fps: 40 }));
var myFxb1 = new Fx.Tween(document.id('demo-inner', {
duration: 'long',
fps: 40 }));
1) try not to copy/paste code from demos. Write it out and you'll
learn more.
2) `document.id('demo-inner',{` should be `document.id('demo-inner'),{`
Fx.Tween takes two arguments: the id or string for an id of an
element, and an options object:
new Fx.Tween(element, options);
I actually can't believe your code even works in the other browsers.
You can simply do:
new Fx.Tween('demo-inner', {
// your options
}
On Dec 29, 2009, at 12:07 PM, Ami wrote:
It's a little extensive to put on shell since it's the entire site
that's tweening... :/ My apologies.
Basically, the entire site is in one very large div with smaller div
"pages" within it, and clicking the navigation links at the top of
each "page" tweens the entire div to a different "page."
On Dec 29, 12:58 pm, Ryan Florence <[email protected]> wrote:
1) What is supposed to tween?
2) Will you put the code in question up onhttp://mootools.net/shell/?
On Dec 29, 2009, at 11:56 AM, Ami wrote:
I'm having a very strange problem with an Fx.Tween instance on a
site
I'm working on.
All of the links work perfectly in IE except for the links on the
home
page! I can't find any differences in the code between "pages,"
they
all appear to be exact duplicates of the others.
Does anyone have any idea why this might be happening? The code I'm
testing is athttp://www.3wayevents.com/index_ie.html. (Please
excuse
the commented code...I'm tracking changes.)
Thanks in advance.
