Menu Disappears onMouseOver in Firefox

jtrout · Post by **jtrout** » Thu Sep 16, 2004 10:48 pm

I'm stumped, hopefully a second pair of eyes will do the trick! The image that fires the menu looks fine on load, and the menu does popup when you mouse over the "Navigation" graphic in the top left of http://protolive.educause.edu/content.asp?section_id=26. However, as soon as you mouseover the image, the Navigation graphic vanishes, and takes the menu with it! I've upgraded Firefox to 1.0PR hoping that would do it, and Milonic to 5.48, but neither did the trick.

Anyone have any ideas? This doesn't happen in IE6, btw.

Thanks!

Post by **Ruth** » Fri Sep 17, 2004 3:53 am

Hi,
I just wanted to let you know that it doesn't appear in IE5.5, nor Opera. And, I'm not getting the milonic_src.js file downloading to my temp internet files. I do get the mmenudom.js file.

Ruth

jtrout · Post by **jtrout** » Fri Sep 17, 2004 4:08 am

Really?! That's odd, the src is included the line before the mmenudom. That's so weird. I'm going to really have to look at the structure of that code.

Thanks!

Post by **John** » Fri Sep 17, 2004 4:23 am

It appears you have been messing with the code files, including removing the copyright notices, which clearly state...

All Copyright statements must always remain in place in all files at all times

Further, the JS calls are not as we supply them, and the ns4 mod is missing (I know - it's a garbage browser anyway).

Please reload the complete code files and calls as you received them, and then we'll be able to help out.

jtrout · Post by **jtrout** » Fri Sep 17, 2004 5:48 am

What in God's name are you talking about?!

The only files I use are mmenudom.js and milonic_src.js. I don't do anything in the way of modifying them - I copied them directly out of the zip file of the latest version, just today. The only Milonic file I modify is menu_data.js, and that doesn't contain any copyright statement anyway.

The js calls are *exactly* as you supply them. The only calls that I've ever modified have been popup and popdown (at the suggest of your support staff). That modification consisted of putting a function in front of it that does some work before calling the original, untouched popup/popdown function. I'd be interested to hear what function(s) you think I've modified!

And it's our decision not to support NN4, and from what I've seen, that's not against any terms of use of the menu. In fact, it's been discussed on this board, and I haven't seen anyone say it's not acceptable.

Can you please try to be constructive, instead of throwing out accusations? I'm offended by your post.

jtrout · Post by **jtrout** » Fri Sep 17, 2004 6:13 am

You know what, I think I know why you're seeing what you are, and I apologize for not checking on this first. It's a little late - 11 PM is not an easy time to get ahold of our staff

We use xcompress to keep our filesizes down. Here's what's causing the problem:
http://www.xcache.com/home/default.asp?c=65&p=754
Note the first paragraph:

White space compression and normalization removes non-essential characters and standardizes syntax in HTML, JavaScript, and CSS in order to gain even more performance out of the compression engine.

I assure you that the Milonic files on the server are absolutely untouched. Unfortunately, they get butchered going through the compression routines. Let me see what I can do tomorrow to turn off the compression for javascript files.

Sorry for the misunderstanding!

Post by **Ruth** » Fri Sep 17, 2004 7:22 am

You mean you actually got some staff at 11pm? wow

That compression may be why the milonic_src.js is not being downloaded to the temp internet files???

Ruth

Post by **Andy** » Fri Sep 17, 2004 11:16 am

Hi,

It would be great if you can sort the copyright notices out and keep the link-back to milonic.com, without them it really doesn't make it worth our time and effort. It's like working for free, it's very silly thing to do.

Anyway, on to the problem. Is there any reason why you need to place the "Main Menu" inside the table cell. If I move it into the menu_data.asp file, it works perfectly.

-- Andy

jtrout · Post by **jtrout** » Fri Sep 17, 2004 3:04 pm

Of course, Andy, I have a couple people working on it this morning. Believe me, we're taking this very seriously - Milonic is a great product that we really believe in

Post by **Andy** » Fri Sep 17, 2004 3:28 pm

Just out of curiousity; what are you using to compress your files?

It's always good to have info on this kind of things for future reference.

Cheers
Andy

jtrout · Post by **jtrout** » Fri Sep 17, 2004 3:56 pm

XCompress by XCache. I believe we use the ISA version, but it could be the IIS version. It's an ISAPI filter that does a very nice job of compressing outgoing traffic. But, as we've seen here, it can wreak havoc on beautiful JavaScript

jtrout · Post by **jtrout** » Fri Sep 17, 2004 4:01 pm

By the way, Andy, you were right on about the menu definition going into menu_data fixing the problem. Worked like a charm! Thanks so much - I'm really sorry about the misunderstanding. We're working on excluding the Milonic files from the compression, I hope to have a resolution before this site goes live tonight.

Thanks again!

jtrout · Post by **jtrout** » Fri Sep 17, 2004 7:38 pm

We're still working on a way to exclude the Milonic files from our compression filter. In the meantime, I've added your copyright statement to the footer of every page in our site. I hope that will suffice!

jtrout · Post by **jtrout** » Fri Sep 17, 2004 8:13 pm

Even better - we've been able to exclude the Milonic source files from the compression. I think we're back in business!