Welcome to WebmasterWorld Guest from 23.22.46.195

Forum Moderators: incrediBILL

timelines/slideshow

why not in firefox

   
2:23 am on Mar 18, 2008 (gmt 0)

5+ Year Member



What would cause a timeline created in Dreamweaver to work in every browser window except firefox? I am trying to add a slideshow to my home page and testing it from my server and I kept getting one picture, it would not loop it wasn't until I tried opening it in other browsers that I noticed it was only firefox doing this.

thanks

2:30 am on Mar 18, 2008 (gmt 0)

10+ Year Member



Our office staff stopped using Firefox for such problems...not really problems...but the browser just sucks.

Of course you may disagree...

[edited by: BaseVinyl at 2:31 am (utc) on Mar. 18, 2008]

4:40 pm on Mar 18, 2008 (gmt 0)

WebmasterWorld Senior Member rocknbil is a WebmasterWorld Top Contributor of All Time 10+ Year Member



What would cause a timeline created in Dreamweaver to work in every browser window except firefox?

I am presuming by "timeline" you are talking about the Javascript code generated by DW when you use it's animation features.

There are literally **dozens** of reasons why. I'll list a few I can remember. the bottom line is going to be this is not a problem with FireFox, this is a problem with Dreamweaver's Javascript. :-)

- Invalid doctype/Quirks mode: If the doctype is technically invalid, or there are coding errors in the page, this will throw it into quirks mode, and many features may not work. Generally this applies to CSS selectors, but since you are doing animation via Javascript, it may have an effect.

- Deprecated Javascript: I just upgraded to CS3. Lo and behold, an auto-published Flash file **STILL** generates "<script language="Javascript"> instead of <script type="text/javascript"> This in itself is no real problem, but it's an indicator the MM/Adobe generated JS is sorely out of date. To wit,

- Browser identification methods: Any seasoned programmer will tell you: never, ever, ever create anything that relies on the correct identification of a browser. These change over time and it becomes a maintenance nightmare. You test for reliable objects in the DOM, and if they don't exist, degrade gracefully. An example:

DON'T
if ((browser == 'NN') && (version < 5)) { do_something_that_will_break; }

DO
if (document.getElementById) { do_something_reliably; }

In my above test with Flash I noted there is still coding relating to browser identification. This is really, really dumb. :-)

Your problem most likely lies here. It becomes even more critical using DW animation, because this generates references to divs (and the programming may still call them "layers") that must be absolutely positioned and repositioned over the timeline. It's most likely the code does not adequately test for FireFox.

Look to your Javascript, this will be the problem.

Our office staff stopped using Firefox for such problems

You didn't stop because FireFox sucks, you most likely stopped because you incorrectly identified the real problem. FireFox is way faster, extensible, configurable, and less problematic than IE can ever hope to be. Most of the things that work in IE that don't work elsewhere are because the programmer applies browser-specific methods and doesn't know any better.

 

Featured Threads

My Threads

Hot Threads This Week

Hot Threads This Month