4 Replies Latest reply on Apr 16, 2009 11:10 AM by chrisrubal

    Firefox button rollover issues

    chrisrubal

      Strange one... I have a flash file that works in every browser, except Firefox.  In Firefox, it appears that the Y coordinate is "off". You can only use the button when you are approximately 200 pixels down the screen.  I've tested in Chrome, Safari and IE 7 with no problems.  Any ideas?  FYI..the only other info I've been able to find may point to wmode, which in this case I have to set it to transparant so the drop down boxes above the flash movie stays "over" the video.  Here is the link.

       

      http://www.kucourses.com/ec/media/store/mediate/ED532/ED532_9/unithome_tutorial.html

       

      Any ideas?

        • 1. Re: Firefox button rollover issues
          David Stiller Level 2

          chrisrubal,

           

               Interesting.  When I test that URL, the button seems just fine for me in Firefox.  The hotspot is positioned exactly where it makes sense (same for IE, Chrome, and Safari, all on Windows).  Does this issue persist for you when you clear your cache in Firefox?

           

          > the only other info I've been able to find may point to wmode,

          > which in this case I have to set it to transparant so the drop

          > down boxes above the flash movie stays "over" the video

           

               A setting of "transparent" does allow Flash content to appear under other HTML elements, but you really only need "transparent" when the Flash content includes transparency.  WMODE is known to be a bit dicey (has been since its introduction), but anecdotal evidence suggests that "opaque" is a bit less problematic, and both of those -- transparent and opaque -- let your layer your SWFs behind CSS menus.

           

               Not sure if WMODE is the cause for your issue, but opaque is worth a shot.

           

               Here's a bit more info:

           

               http://www.quip.net/blog/2006/flash/how-to-position-flash-beneath-other-content

           

           

          David Stiller
          Co-author, Foundation Flash CS4 for Designers
          http://tinyurl.com/dpsFoundationFlashCS4
          "Luck is the residue of good design."

          • 2. Re: Firefox button rollover issues
            chrisrubal Level 1

            Well... that is strange.  I've had a few people test with Firefox (all windows) with the same negative result.  Strange you dont' find the same thing.  I will try opaque and report back what I find.  Thaks for the tips.

            • 3. Re: Firefox button rollover issues
              David Stiller Level 2

              chrisrubal,

               

                   Aha!  I do see it.  Sorry for my miscommunication.

               

                   I had only checked the centered Play button in the video area.  On the left nav, I do indeed see exactly the y-axis issue you described, and only in Firefox.  So ... yeah, this is odd.  (Again, apologies for giving you the wrong impression in my previous reply.)

               

                   My next questions, then, are:

               

                   a) does this issue occur when you omit WMODE altogether (that is, leave it at its default, "window")?

                   b) how did you set up these buttons in Flash (normal buttons, or anything special going on with the Button.trackAsMenu property)?

               

               

              David Stiller
              Adobe Community Expert
              Dev blog, http://www.quip.net/blog/
              "Luck is the residue of good design."

              • 4. Re: Firefox button rollover issues
                chrisrubal Level 1

                Ok..just to make it more confusing.  When I go to the direct link for the file, it works, perfectly in Firefox.  You see.. the way it is published, the HTML, CSS, Javascript generated by Lectora is on one server, the video and flash files are on another.  When I publish and view locally in Firefox...no problem.  But once I move the HTML and associated files up to server, it creates this issue. So, I think we've boiled it down to an issue with the way Lectora is publishing it.  I'm moving over to that forum.  Thanks again for your help.