CSS Menu - Hamburger Menu Support

[VPXMedia]

Hello, we are still suffering from the lack of a hamburger menu in the CSS Menu object even in WB 18.2, as it's the only menu that supports RTL direction.

Any alternative solutions or plans to add this feature soon? Unfortunately, using external menus' HTML/CSS code doesn't work properly in WB because it usually breaks the page.

[Pablo]

The CSS menu was not designed to have a hamburger menu, because it's a 'CSS only' menu. So, there are no plans to add this because then it would not longer be a 'CSS' menu.
There are several alternative (JavaScript based) menus that do have a hamburger icon.
For example;
- Responsive menu
- Mega Menu
- Dropdown menu
- Themeable menu

And many of the navigation extensions have a hamburger icon
https://www.wysiwygwebbuilder.com/navigationpack1.html
https://www.wysiwygwebbuilder.com/navigationpack2.html
https://www.wysiwygwebbuilder.com/navigationpack3.html
https://www.wysiwygwebbuilder.com/navigationpack4.html
https://www.wysiwygwebbuilder.com/navigationpack5.html

Also, all menus that work elsewhere will also work in WWB. WWB does not break it. The code will be inserted "AS IS"!
If the code does not work then either is invalid or you have added it the wrong way.

[VPXMedia]

Many thanks Pablo for the detailed response. I usually use the feature-rich Responsive menu for normal LTR menus, but the menus you mentioned don’t support RTL menu system. So I have to stick with the CSS menu. Adding full RTL support to the Responsive menu (like you do in many WB tools and components) would be greatly appreciated for many WB users who have clients that require RTL versions of their websites.

The problem with using external menu modules is that they interfere/conflict with standard WB CSS code and IDs, causing different errors on the website pages.

[Pablo]

You can post suggestions here:
viewforum.php?f=28

If more users find this useful then I will consider it for future development.

The problem with using external menu modules is that they interfere/conflict with standard WB CSS code and IDs, causing different errors on the website pages

In that case, why not update the IDs?

I don't think it's fair to blame for WWB for external code not working, because the code will be inserted "AS IS". WWB does not modify code to make it 'not work'.
So, if the code is correct then it will work the same as anywhere else...