My homepage works fine safari, but not in Firefox. It’s just got 5 slave images that fade in/out using the sequence timer. Surely this is pretty simple and should work in FF?
The Prototype libraries are being added to the page twice. It becomes a bit of a crap-shoot how browsers will actually handle this. Some perform admirably with these double declarations, others tend to buckle.
Either way, this double-declaration is incorrect, so, arguably, neither browser behavior is really better than the other.
[[ I see protopacker.js at the top of the html document, and a second declaration in the lightbox area a bit further down. The protopacker.js bit is being added via the fade-in action(s). It appears this lightbox info is potentially being added either via an ‘extended’ attribute or some server-side script/include ]]
Are you using the latest version of FW5? There was a bug that affected me with rollovers and slave layers in Firefox in 5.0.0. It was cured for 5.0.1 and now all works fine for me. Maybe it affected the sequence timer too…
Pete
On 29 Apr 2008, at 12:41, Nathan Garner wrote:
My homepage works fine safari, but not in Firefox. It’s just got 5 slave images that fade in/out using the sequence timer. Surely this is pretty simple and should work in FF?
Are you using the latest version of FW5? There was a bug that affected me with rollovers and slave layers in Firefox in 5.0.0. It was cured for 5.0.1 and now all works fine for me. Maybe it affected the sequence timer too…
Pete
On 29 Apr 2008, at 12:41, Nathan Garner wrote:
My homepage works fine safari, but not in Firefox. It’s just got 5 slave images that fade in/out using the sequence timer. Surely this is pretty simple and should work in FF?