Christian Robottom Reis
kiko at async.com.br
Mon Dec 8 16:14:34 UTC 2003
On Mon, Dec 08, 2003 at 04:56:14PM +0100, Ludovic Dubost wrote:
> >I think my example was not clear.. My point is to use the same names
> >for things that have a good chance of looking the same accross pages.
> >For example:
> > -> of course the banner; the footer
> > -> the actions for bug views or the next/prev links in bug list
> > -> a section with advance fields,
Ah, you mean classes that can be used in multiple pages, and use
advanced fields as an example. Gotcha.
> >>I think that <li> is really the way to go for the top-level actions,
> >>though, and we might be able to tolerate some visual changes to allow
> >I thought it in the beginning to since the <li> reprensents lists and
> >that it makes sense for menues to be lists..
> >However when I saw the result without style sheets I really didn't
> >like the result.. For TV terminals or PDA it is true that you will see
> >the items but it won't be as nice as it is now.. The following article
> >(sorry in French: http://openweb.eu.org/articles/initiation_display/)
> >showed the tric to have a better accessibility using the | as it is in
> >bugzilla now..
You could use that trick in conjunction with <li>s -- the issue is if you
want them rendered as list items when no CSS style is available. I think
that screen readers would appreciate it, and that generally speaking
it's the "right thing to do", but I'm not sure and would appreciate
third-party comments here.
> Here is the div structure I'm using in my template which allows to
> customize quite well the interface to my needs..
> (it only shows the divs, not what is inside)..
But I miss the <h1-hn> tags which provide us with actual page structure.
Did you not use them?
The example is interesting, thanks for it.
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the developers