Hi,
I recently reopened a project in Freeway after not touching it for several months and a few FW upgrades. I did some light text edits on the site and now the drop down menus aren’t displaying color. The only drop down is under the “Programs” menu item. I can see the text highlight when I scroll down, so the menu is dropping down, but the blue background color is missing. Help!
Thanks in advance!
John
Hi Simon,
Thanks for your reply. I’m using the MenuBar action item to do this. Previous to opening the site doc in the newer version of FW (I got a “previous version” warning when I opened the doc) I thought that simply coloring the table containing the submenu items would apply that color to the submenus. At least that’s how it appeared to operate before as the menu was displaying properly before reopening the document in the newer version of FW.
So, I’ve got a table object named “menubar2” that has the Menu Bar action applied. In the top section of the Menu Bar action palette options, I’ve set my link and hover colors, and the “Background” option “None” (I tried applying the color I want there but it doesn’t make any difference). In the lower part, I’ve designated another table “menu-items” as the source for the submenu items. Link and hover colors are set, and “Appearance” is set to “None”.
Odd thing is, it all worked fine before I opened the doc in the new version. What’s changed?
Hi again Simon,
Looking a little deeper, it looks like the previous version of FW might have been something like 5.5 and now I’m using 7.01. I’m guessing the Menu Bar action is no longer supported? Guess I’ll study up on the CSS Menus action…
Menu action is still, there though I’ve no experience of it! Do you not just use the colours palette to set the background colour of your second table??
This has not only styling purposes but more semantic reasons.
What you’ve got now is a theoretically visualized “Menu”, but in fact it isn’t. It’s just a cluster of unrelated links and no search-bot or screen-reader would recognize it as a menu.
A nav attribute is (IMO) un important page-element to declare your work what it is:
A project with related pages, while currently it’s an index page with tons of unspecific links to goals that can be parts of the project but as well pointers to “satellite pages”.
For a quick-start in this world, I once wrapped this into following (naive) article:
Thanks Thomas and Trev for your input. I’ve gone around the issue by using the CSS Menu action. I like it better actually and can see why it’s a better choice.
Cheers, John