No, but you should hook up FireBug or Fiddler to see what is actually being sent.Is there maybe some JavaScript code that's executing on menu item activation/deactivation? Still - I would expect that to fire in all browsers. IAC, if you hook up firebug you should be able to see the http requests being initiated and potentially you can set a break point in the menu's code to see where the remote calls activate from.
+++ Rick ---
I noticed an odd problem today in Firefox that doesn't happen in IE. When I click on the menu and just pull the cursor across the menu items, it sends a hit back to my WWWC app. This is all when running locally, with the WWWC app in File mode, so I can see the hits happening each time I move across a menu item. The menu is a JavaScript menu - standard dropdowns and cascading dropdowns - and just moving the mouse across the choices should not generate any hit to the server. It doesn't in IE, but it does in Chrome. Really kind of odd. Anybody seen this behavior before?