i dont expect this added logic to be 100% foolproof, but if the code that outputs the top nav bar could add a check based upon user agent, that'd be awesome ... something like perhaps if USER_AGENT != lynx { <show top nav bar> } it's just that it's a pita to scroll through Home/About/Social Contract/etc... when using cmdline browsers ... and really, if you're on bugzilla with a cmdline browser, you're not there to browse the other gentoo sites ;)
mike, i was just looking at bugzilla using the links http client, and it looked fine. is this still a valid request? -jeff
it depends on what you mean by 'fine' i tried bugs and bugstest with links and the both show the non-bugs navbar at the top ... specifically, imo, these links should not show up: Home | About | Docs | Forums | Lists | Bugs | Planet | Store | GWN | Get Gentoo!
Moving open bugzilla bugs to the new bugzilla group (because I'm about to stab lots of these bugs).
the header takes 4 lines in lynx, and 3 lines in links. That's not too far to scroll.
you misunderstood what i meant by "scroll" sure it's 3/4 lines, but it's almost 20 links, each of which is given focus ... so you have to arrow through (scroll) past each link in order to get to the search fields
Ok, I'll look into something better. Does lynx/links implement ordering of links per the accessiblity attributes?
no idea
Ok, finally figured out how to do this in the templating language. Done now.