SpaceGirl said:
It doesn't work. It ONLY works fully in non-IE browsers (it uses :hover,
which is not supported on anything but links in IE),
that's why there is a bunch of JavaScript to help IE to get it correct
and along the W3C specs. although it will work with switched off
JavaScript in terms of having accessibility to the content...
and to get it to
work in IE you need to use their JavaScript fudge. So this is NOT a real
solution.
in my view it is. it's the far sophisticated solution I know to overcome
the lack of a drop-down menu.
But I guess the OP didn't say he wanted it to work in all
browsers
it works on all browsers, because it makes use of a list. it depends
what you mean with 'work'. If you claim 'pixel accuracy' as 'working',
then it will not work. But then you will have a big problem as a
webdesigner: to claim your site will be pixel accurate on all browser (I
prefer the term UA) is impossible, and you might have to sit back and
reflect a bit about what webdesign actually is.
As far as I understand webdesign accessing the content is 'working',
beause people demand for the content. So the proposed solution will
'work' decently on all modern browsers (even on Netscape 4.x as the
colapsed list will be displayed, and even on a Lynx text browser you can
access the full menu, without noticing anything weird...)
basic philosophical question: are we going to write XHTML according to
the specs or according to the browsers weirdness?
I have decided to write along the specs, because I don't know what sort
of browsers my viewers are going to use in the future.
And with the growing availabilty of FF we will see IE's distribution
drop... so no need to be afraid of the above method
bernhard