Menu Widget help

Question

Using CSS and a body ID per page, how can I tweak the menu
widget to highlight the page I'm on? It's a standard CSS trick, but
I can't get it to work with the widget. You just ad an ID to the
body, and extend the rules to apply only to a particular page. But
no matter what I do, the widget classes overrwite my changes. Is
there some way to do this?
I can't be the first person to want to do this...
Thanks
Doug

Answer 1

"dbonneville" <[email protected]> wrote in
message
news:erfef7$t69$[email protected]..
>I was attempting, at one point, to implement suckerfish
until I came
>across the
> caveat that the LI elements HAD to be fixed width or
Opera would break
> (see the
> "Son of Suckerfish" article). I was looking at your CSS
and noticed
> the LI was
> fixed width, and assumed it was for the same reason. All
the menus I
> looked at
> (dropdowns) on your site had fixed width - maybe I
missed a menu that
> was not
> fixed with AND a dropdown. Can the LI elements in fact
have no width
> assigned
> so that they simply conform to the size of the text they
contain?
I'm not all that fond of Suckerfish :-) I like this approach
better, as
it degrades better and the script is a lot more
straightforward:
http://www.projectseven.com/tutorials/navigation/auto_hide/workpage.htm
> I noticed your Tabbed (or was it panel?) solution had
variable width
> to
> accomodate the text, but it was not a dropdown per se,
but a second
> row of
> navigation.
It's a horizontal list. Esssentially the same type of
construction as
the root. The problem with dropdown menus is that you more
than likely
want the links to be blocks - to appear and behave like
images. If they
are declared as blocks, then their boxes can certainly be
made to
collapse, but it will look funny. If you don't want them to
be blocks,
then they can conform to the least wide link lext, but it
will not look
too pretty.
> On another note, I did fix the specificity issue with
the menu
> widget - I
> wasn't being specific enough like you suggested. I also
ditched the
> javascript
> I wrote in lieu of the more simple method of using a
unique page ID
> and setting
> the "current page" by utlizing specific CSS rules based
on those IDs
> and
> corresponding elements.
>
Glad you got it working.