1 Correct answer
I copied one composotion to see, that there are no rollover states (no states at all) set up.
Your menu with the intended states is just covered by the composition (tooltip), meaning it is covered by the trigger.
That´s why, hitting just the border of the menu shows the rollover state indeed.
I would use single tooltips instead of a menu, although the menu makes everything a litttle more comortable (you may think).
You could then link each menu item/composition to whatever page you create:
This appro
...
8
Replies
I copied one composotion to see, that there are no rollover states (no states at all) set up.
Your menu with the intended states is just covered by the composition (tooltip), meaning it is covered by the trigger.
That´s why, hitting just the border of the menu shows the rollover state indeed.
I would use single tooltips instead of a menu, although the menu makes everything a litttle more comortable (you may think).
You could then link each menu item/composition to whatever page you create:
This approach makes it easier for your mobile resolution to get everytrhing in the right spot.
Leads to your dropdown, which is of course easy with the menu widget itself. I can see the menu item in browser
but it will get out of place very soon after the 960:
Everything should be inside the blue thin guides. Of course I don`t know, what your plans are for mobiles, but …?
You set up the right symbol to show up with the submenu, I recommend to turn it off instead, it disturbs readability, I think:
Overall/Finally – maybe the design needs some more thinking over, about different devices, about the amount of menu items in one line (maybe it is possible in two or three lines, 3x4 or 4x3 as a block of menu items?).
Hope this helps.
Don`t panic about EOL too much. Nancy is not a muser, although you may need some different app in future, if you already started in muse, finish it there. Once you know what you want and need, it may be easier to search for another app to fit your needs like blocs for mac or pinegrow and transform your design then (I personally cannot recommend DW at all, BTW).
You may find/download your file worked over here:
Best Regards,
Uwe
heinh45867521 wrote
I am new to Muse so please be gentle with the answer.
In case you haven't heard, Muse development has stopped. You might want to switch to another web authoring tool before you become heavily invested in Muse. Going forward, my advice is to use Dreamweaver or a similar code editor.
FYI: The HTML title attribute will produce browser tooltips. No other scripts or widgets are needed.
<a href="some_link.html" title="My Awesome Web Page">MENU LINK</a>
When a user hovers over the link in a desktop browser, they will see the browser's default tooltip as shown below.
There are many advantages to working directly with code. Sadly, Muse makes working with code very difficult.
Really? 
Perhaps this is the case, because Muse is intended for building websites without coding.
heinh45867521, please give us a sample .muse file as I suggested, and we will see, what is going wrong.
FYI: The HTML title attribute will produce browser tooltips. No other scripts or widgets are needed.
<a href="some_link.html" title="My Awesome Web Page">MENU LINK</a>
When a user hovers over the link in a desktop browser, they will see the browser's default tooltip as shown below.
The tooltip browser is not intended here at all, Nancy. Your Code is not necessary here. The browsers tooltip is for disability access only. No design possible. No solution. Not helpfull.
Best Regards,
Uwe
AdChoices