Firefox expanding collapsible menu on load

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lily alayeva
    New Member
    • Apr 2011
    • 4

    Firefox expanding collapsible menu on load

    I am using a collapsible menu for my site. It works fine on all browsers except for firefox.

    On firefox 3.0, the expandable menu loads completely open for a few seconds and then collapses to its closed (home) state.

    I cannot figure out if its a simple tag thats not closed or if there is a larger javascript problem.

    Any help would be greatly appreciated!

    Preview Here
  • gits
    Recognized Expert Moderator Expert
    • May 2007
    • 5390

    #2
    without seeing the code or having a link to the page to have a look at - it is just guesswork to answer this ... so you should provide some more information.

    kind regards

    Comment

    • lily alayeva
      New Member
      • Apr 2011
      • 4

      #3
      There was a link up there (in the preview here line). Here it is again:

      Comment

      • gits
        Recognized Expert Moderator Expert
        • May 2007
        • 5390

        #4
        ah ... overlooked that. opened it in FF and chromium and the accordion is closed onload ... in FF it is closed instantly and in chromium the sara-link is open for a half sec or so. how should it behave to be correct?

        kind regards

        Comment

        • lily alayeva
          New Member
          • Apr 2011
          • 4

          #5
          Ideally, the accordion should be completely closed, until the tabs are clicked. In firefox 3.6 it seems to look fine. However, in 3.0 it opens up on first load and then collapses back in a second or so to its off state.

          Can't figure out why the simple javascript is acting odd in firefox and chrome.

          Comment

          • lily alayeva
            New Member
            • Apr 2011
            • 4

            #6
            Nevermind! I figured it out. It appears to have been just an old version of javascript. Updating to 1.5.2 fixed the problem!

            Comment

            Working...