doctype ruins sub-submenus (non-ie). #9

Poster: flii
Dated: Tuesday September 16 2003 - 19:39:32 BST

i sucessfully customized the sample #9 (dhtml menu table-bound), but when i started adding things to the working page, the sub-submenu managed to break itself. i traced the problem and found that specifying my doctype is what messes it up. note that i'm using mozilla firebird and that ie will display it correctly, even with the doctype.

i don't know if this is a bug with my browser, with the code, or i'm simply doing something wrong. hopefully i got this in the right forum at least.

the site: http://larsondata.com/new

the js: http://larsondata.com/new/menu_data.js

the problem: go to Products -> Financing. the menu off of financing doesn't appear where it should. taking out the doctype at the top of the page fixes it.

Poster: Hergio
Dated: Tuesday September 16 2003 - 20:32:09 BST

I would also recommend taking your menu declaration out of the HTML of the page and putting it back into the js file. And then putting all your SCRIPT includes at that spot in the page where you are declaring the main menu instead.

Poster: flii
Dated: Tuesday September 16 2003 - 20:52:47 BST

ok, i put it in the menu_data.js file (with clarification from this post) but it's still not working correctly.

any strokes of genius come to you?

Poster: John
Dated: Tuesday September 16 2003 - 21:02:08 BST

Drop down from strict to transitional.

BTW, in looking at your page I don't see any functional problems.

Poster: flii
Dated: Tuesday September 16 2003 - 22:11:26 BST

i actually already tried that. it didn't fix the problem so i went back to strict. i'll leave it at transitional so you can see, since i alawys like knowing for sure if the person i'm helping is actually doing what i tell them to do. lol. many times they say they are, but they're not.

oh, as for the functional problems, it works fine in ie. however i'm using mozilla firebird, which is what it's not working in. i haven't gotten around to downloading other browsers (such as netscape/opera/etc) yet so i can't verify if it works or not in them. any input you have on that subject would help as well.

thanks.

Poster: John
Dated: Tuesday September 16 2003 - 22:51:36 BST

Mozilla I don't have, but in Opera7.11, IE6, and NS7.1 it all looks fine.

Poster: Andy
Dated: Wednesday September 17 2003 - 10:30:24 BST

There are issues with Firebird and DTD

I'm tempted to wait until Mozilla have gone full release but as always people expect the browser and menu to work.

The problem we have is that Firebird is working differently to other Mozilla based browsers when DocTypes are used. I'm not sure if this is intentional or will be fixed in the final release.

If you can find out what Mozilla's plans are in regard to DocType it would be a great help.

At the moment we will need 2 sets of code. One for DocType the with for no DocType and this is very inefficient.

Cheers
Andy

Poster: flii
Dated: Wednesday September 17 2003 - 14:46:04 BST

thanks andy. i figured it might have something to do with phoenix, since i know it's not ready for normal public use yet, but i wasn't sure. truthfully, this is the first problem i've had with phoenix not rendering a page correctly, so while i knew it was possible i simply hadn't thought it likely. *hits forehead*

i have a big aversion to the original mozilla browser and netscape because of their gui. i like things a certain way, and though they have more compliant engines than ie, i can't stand using them. tg for phoenix - compliance and customization all in one.

now that i know a little bit more about the issue, i did a search of bugzilla, for anyone else who is interested in this. i found no bugs on phoenix for either "doctype" or "doctype dtd", and the closest mozilla bug i found was one on doctype breaking images. if anyone knows more about it, please email me.

thanks for all the help and suggestions.