Hi all,
Posted this the last week... thought it was resolved, I had made a dumb error with an invalid path... but now that it's corrected... a new problem arises.
Last year, Andy helped me by using the menu to design these "pseudo" pull-down menus for this form (cannot thank you enought for that!):
http://rimea.org/forms/allstate/test1.html
After upgrading from 5.727 to 5.735, and then finally the pre-release of 5.736, the pseudo-menu no longer functions in FireFox 1.07. And it seems to be occasionally buggy IE 6.0. (Menu sometimes fails to appear.)
Scroll down to the big table and click into a field, say "Instrument" or "Grade". In FF 1.07... it flickers and never come back.
Here's the odd thing, tab into those fields and it the menu appears perfectly.
Would it be best for me to simply roll back to 5.272 for this form thingy and use the newer version on my main site navigation menu?
Thanks everyone.
~Wayne
still quirky behavior in FireFox... {SOLVED}
Hi,
Try adding the following to your menu_data file (or after the mmenudom.js call)
What this does is disable to body click that hides the menus, it's intefering with your code.
Hope this helps,
Andy
Try adding the following to your menu_data file (or after the mmenudom.js call)
Code: Select all
document.onclick=""
Hope this helps,
Andy
Thank you!... Andy you da' man!
I added it here:
...and now it works again!
We used this form to register a few thousand students for All-State this year... as far as I can tell it functioned perfectly! I simply re-directed anyone with JS disabled and showed them how to turn it back on. (Although I don't think it was ever an issue.)
One more question... if I may be so bold... and this isn't a new issue... and doesn't keep it from working correctly.. but when I use FireFox... there has always been a bit of distortion that appears for a fraction of a second before the larger pseudo-menu generates (Instrument). Do you see it? I guess it would have to do with processor speed?
http://rimea.org/forms/allstate/test1.html
Thanks again!
~Wayne

I added it here:
Code: Select all
with(menuStyle=new mm_style()){
oncolor="#ffffff";
offcolor="#000000";
onbgcolor="#316ac5";
offbgcolor="#ffffff";
bordercolor="#000000";
borderwidth=1;
padding=2;
fontsize="90%";
fontstyle="normal";
fontfamily="Verdana, Tahoma, Arial";
status="";
clickfunction="setText()";
borderwidth=1
document.onclick=""
}
We used this form to register a few thousand students for All-State this year... as far as I can tell it functioned perfectly! I simply re-directed anyone with JS disabled and showed them how to turn it back on. (Although I don't think it was ever an issue.)
One more question... if I may be so bold... and this isn't a new issue... and doesn't keep it from working correctly.. but when I use FireFox... there has always been a bit of distortion that appears for a fraction of a second before the larger pseudo-menu generates (Instrument). Do you see it? I guess it would have to do with processor speed?
http://rimea.org/forms/allstate/test1.html
Thanks again!
~Wayne
Thanks John! It's mostly's Andy's handiwork, though.
I added a JS "dependency" validation script this year... on the actual application page, in the table for listing students... a sponsor cannot submit the form if a name is entered in the first column "Name" and the any of the remaining fields are left blank. It will say "ERROR - John does not have an instrument". But it allows for completely blank rows... and the form script itself actually ignores empty rows in the final output so it all looks neat and pretty.
~Wayne
I added a JS "dependency" validation script this year... on the actual application page, in the table for listing students... a sponsor cannot submit the form if a name is entered in the first column "Name" and the any of the remaining fields are left blank. It will say "ERROR - John does not have an instrument". But it allows for completely blank rows... and the form script itself actually ignores empty rows in the final output so it all looks neat and pretty.
~Wayne