Blooming IE and menus

Dear All
I really would appreciate any help anyone could give me because I am going nuts with it!
Please take a look at
http://homepages.nildram.co.uk/~eldon/menus/brig5.html
where you will see my attempt to create a website for a local church.
Problem is the onclick menus work nicely in FF and NS, but in IE6 they disappear as soon as you roll over them. I have tried for several hours to try and stop this happening, but it seems to me that IE is being a bit tempremental - actually, I am sure its my css!
Many thanks
Edward

You need a .htc file so IE will handle the psuedo class :hover on an ul li element etc. This will do the job. http://www.xs4all.nl/~peterned/csshover.html I have a sample of this in action at http://www.newbeginningsdesign.com/s...thumb_gallery/

BTW I didn't check your code so not sure on your methods but you can/should do it with 100% CSS and then include the .htc file (Which will bork your CSS validation because of the call in the CSS) but that is not a big deal and only IE will require it so any other browser will work with js on or off.

Hi thanks for the replys.

However, I am not sure that this is the problems since I am using

#menu li a:hover

ie hover as a pseudo of a.

Also it worked perfectly before I put it within the context of the rest of the header (ie the menu worked fine on its own) and only appeared to screw up when I put the containers and so on in as well. Also I find that sometimes the menus work, and sometimes they don't - it all seems a bit erratic...

Sorted - went and stripped it right down,and now it works

Funny old thing life!

I know you didn't ask for this type of opinion, but you can take it or leave it, no harm no foul.

Please consider using a single level navigation menu down the left side. When dealing with churches it's absolutely gauranteed you will have elderly visitors. Pull down menus function terribly for elderly people. They have a hard enough time getting the cursor over the menu item to begin with and now they must maneuver down to a second item without causing the pull-down to disappear when they move off of it.

Anyway, you don't have take my word for it, do some beta testing.

As for my testing, soon as I attempt to move to an item in the pull down it disappears. Every now and then it stays up, sort of like a sweet spot or something. Not very functional.

The disappearing is the whole problem - but I think that is sorted now.

As to the "Old people" issue - a good point, and not one I had thought of. Um. Interesting.

Yeah church web sites are tricky like that. I am about to do one for my church. For some reason I like doing pro bono charity work eh....! A simple solution would be to simple make sure the top level of the menu's works and you could also provide the links and sublinks on a side bar or something based on the page the top level of the menu hits. That is if you really want to keep the menu. You are really going to need to work accessibility into a site like this i.e. works with CSS on or off (No tables!) Works with JS on or off (Top level menu links + sidebar with section links?) and of course make sure it works in large and small font sizes without breaking and really put focus to your information architecture. Accesskeys, title attributes on links, alt tags on images etc etc...

Hope that makes sense.

So say you have menu bar at top then also a per page side bar

[Link] [Link] [Link] [Link] [Link]

Link
Indented Sub Link
Indented Sub Link
Link