Alan Henness
posted this
28 October 2020
That is how the Nicepage mobile menu works. I mean the menu item that has subitems always works as a separator in the mobile menu as the hover state os not defined in the touch devices. There is no way to change this behavior.
I have just encountered this problem. I can understand that in the hamburger menu, when a menu item is clicked, it has to open any sub-menu items (so they can be seen), but can't it also open the page that is attached to the main menu item? That would be behind the menu panel but would be seen and show fully when the menu is closed.
The problem with creating a separate hamburger menu as you suggested is (if I understand it correctly) you have to duplicate the menu item for the higher level menu item in a sub-menu so it can be clicked on separately.
For example, for a standard header menu:
Menu item 1 | Menu item 2 | Menu item 3
Sub-menu item 1
Sub-menu item 2
Where Menu Item 2 is linked to a page and also has one or more sub-menu items
For the 'equivalent' hamburger menu, it would need to be:
Menu item 1
Menu item 2
Menu item 2 [this is needed so it can be clicked on]
Sub-menu item 1
Sub-menu item 2
Menu item 3
The same applies every time a menu item links to a page and also has sub-ment items - is not just at the top level but also at lower levels. This seems cumbersome and creates more work to keep updated as two menus have to be updated for any changes.
Have I understood this correctly and is my suggestion of opening that page when the menu item is clicked (as well as expanding the sub-menu) feasible?
The only alternative I can see is to abandon ever having menu items (that have sub-menus) from opening their own page.
> That is how the Nicepage mobile menu works. I mean the menu item that has subitems always works as a separator in the mobile menu as the hover state os not defined in the touch devices. There is no way to change this behavior.
I have just encountered this problem. I can understand that in the hamburger menu, when a menu item is clicked, it has to open any sub-menu items (so they can be seen), but can't it also open the page that is attached to the main menu item? That would be behind the menu panel but would be seen and show fully when the menu is closed.
The problem with creating a separate hamburger menu as you suggested is (if I understand it correctly) you have to duplicate the menu item for the higher level menu item in a sub-menu so it can be clicked on separately.
For example, for a standard header menu:
Menu item 1 | Menu item 2 | Menu item 3
Sub-menu item 1
Sub-menu item 2
Where Menu Item 2 is linked to a page and also has one or more sub-menu items
For the 'equivalent' hamburger menu, it would need to be:
Menu item 1
Menu item 2
Menu item 2 [this is needed so it can be clicked on]
Sub-menu item 1
Sub-menu item 2
Menu item 3
The same applies every time a menu item links to a page and also has sub-ment items - is not just at the top level but also at lower levels. This seems cumbersome and creates more work to keep updated as two menus have to be updated for any changes.
Have I understood this correctly and is my suggestion of opening that page when the menu item is clicked (as well as expanding the sub-menu) feasible?
The only alternative I can see is to abandon ever having menu items (that have sub-menus) from opening their own page.