The issue at hand is that [productname] is completely compliant, but is more modern than HTML 4.01. If you remove the doctype tag, all your rendering issues should be resolved.
This is sooo untrue. If they require invalid HTML, their product is NOT compiliant.
Funny you reach that conclusion just on the OP's mail (in which te makers of the menu state it to actually be compliant!). If the menu at hand is written in valid XHTML strict, for instance, putting a HTML4.01/trans DTD in top of the html _will_ cause validation issues and _might_ cause rendering issues.
If you remove doctype, browsers emulate IE5 invalid CSS interpretation. Far from being modern.
I would dare say that this is at best partially true. Opera sure tries to emulate IE when it is told to do so (and even emulates some parts of IE's behaviour while in 'Opera' mode), but I'm not so sure that a Gecko in quirks mode mimics IE on purpose.
Removing the tag will solve your rendering problems.
...will cause...
Why?
I'd get rid of that menu. It *needs* browser *bugs* in order to work! Is this menu accesible when: - javascript is off? - styles are off? - styles and js are off? - keyboard is used to navigate?
The sequence of your advice and questions suggest you are assuming all answers to be 'no' beforehand, whilst you haven't seen any line of the menu code whatsoever.
I'm sorry if my reaction feels a bit harsh, but jumping to conclusions like this just doesn't help the standards' case, does it? ;-)
Jeroen
-- vizi fotografie & grafisch ontwerp - http://www.vizi.nl/
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
