I am getting a little frustrated with the responsive menu in this example. The logo on the left is linked to the homepage but you will notice that only the top half of it is active. The bottom seems to be being ‘blocked’ by the responsive menu… but only when the alignment setting in the action itself is set to ‘center’
Hi Dave, yes there was some weird code in there so I have stripped everything out and made a new file from scratch and still no joy. The more I look at this, the more I think it may be a bug. I have been in touch with sp support too but no joy so far.
Close up the browser window until just before the menu tucks under the logo and the link does not work on the bottom half of the logo. The above example is with the menu alignment dropdown in the ‘size and shape’ section of the action, set to ‘center’
This is with the alignment set to ‘right’ (it is also fine when set to ‘left’)
‘menuWrapper’ is the parent div that holds the menu item and can be seen with a thick green border,
‘fwNavContainer1’ is the wrapper for the css menu and is shown with a thinner red border and,
‘fwNav1’ is the CSS menu itself - displayed with a blue dotted border
If you close the browser window up so it becomes narrow you’ll notice that the ‘fwNavContainer1’ (red bordered) item slides over and on top of the logo to the left. This is what stops you from clicking directly on the logo when the browser width is narrowed.
Looking at the code I can see that the right position for the ‘fwNavContainer1’ (red bordered) item has been set to 50%. This positions the right side of the item 50% off from the parent which, in turn, throws it far to the left. Normally the menu would appear here as well (‘fwNav1’) but that has been set to left of 50% which pushes the menu items back into the boundaries of the ‘menuWrapper’ container.
Thanks so much for having a look at this for me Tim. I presume you edited the offending code externally?
Is there a way to do this within FW so I don’t have to do it each time I update/republish?
I’m wondering if this is a bug? When I open the file in text wrangler directly from the preview button in FW, I can see the code so I wasn’t sure what you meant when you said the FW file didn’t have the issues?