We're going in circles here.
> showed you an example of a multi column div in a sub,
> had tags, image, and assorted other markup
> did you even look at it?
> Plugin code was untouched, any adjustemnts were done with css
Yes i did look at that example, and analyzed the HTML code for it. Yes
showed you an example of a multi column div in a sub, had
tags, image, and assorted other markupdid you even look at it?
Plugin code was untouched, any adjustemnts were done with css
Florent V. wrote:
The exact same markup in YUI example bellow works perfectly well...no hac
> The exact same markup in YUI example bellow works perfectly well...no
> hacks needed
In my experience, it doesn't work. As i wrote earlier, most Superfish
functionality will work, but if you use something else than a UL as
your submenu, even if it's just wrapping a UL in a DIV for styling
superfish shows and hides UL's and doesn't interact with their children
like you are saying. The exact same markup in YUI example bellow works
perfectly well...no hacks needed
Florent V. wrote:
Thanks for this example.
there's no doubt in my mind that YUI team hasn't proc
Thanks for this example.
> there's no doubt in my mind that YUI team hasn't processed
> all the issues you bring up when making their determinations
> on structure
I don't know if they have. The YUI developers are very capable people,
but this does not totally guarantee that YUI is accessible or
When it comes to issues like you are presenting I defer to higher powers
Example: YUI framework, even in latest 3.0 release. Menu is built with
UL/LI with containing DIV structures:
http://developer.yahoo.com/yui/3/examples/node-menunav/node-menunav-3_source.html
here's a live example on Am
> not sure what you mean by "hack" or "abusing the ul/li elements"
HTML 4.01 defines a set of elements, each with its own semantics. Some
are meant as generic wrappers or containers in order to support
language or style information (that's the DIV and SPAN elements).
Others have a more precise me
not sure what you mean by "hack" or "abusing the ul/li elements"
only interpretation can think of for "abusing" is invalidation, here's
an example of large container div inside a sub in superfish.
http://tinyurl.com/yzfwmvy
here's the 100% validation thru w3c validator
http://tinyurl.com/y
> there is no reason not to be able to build a mega menu inside UL/LI structure
> and this has been done in superfish
Sorry, but i think this is a mistake.
This is the kind of code that Superfish expects:
Category name
I don't know a lot about screen reader issues, however there is no
reason not to be able to build a mega menu inside UL/LI structure and
this has been done in superfish.
You can put divs inside an li, with columns , images, H tags, whatever
you want and is all valid. Do whatever css you want
10 matches
Mail list logo
