The biggest issue we found is when dealing with a large menu system, you have a massive amount of unneeded markup twice.

Again the way it works is great in theory, features and usually is great as well, but it needs a complete overhaul of how it puts out the html code as it’s bloated and does not need to be, which makes it slow to load this element, if you think the idea through it can be made so much simpler.

It just creates way to much html output that is just hidden based on css classes, it needs to work off of simple JavaScript breakpoints, that sets classes based on a breakpoint usage, not a complete html output that is all class based and very code heavy.

If you turn off any scripts of css you can see the code it puts out.

Look at Bootstrap as a great example of this, they have been doing this idea since Boot Strap 3 and 4 and now 5
REF: https://getbootstrap.com/docs/5.3/layout/breakpoints/#core-concepts

That is our biggest issue and somehow you guys really need to look closer on how this header builder works, it’s sadly highly flawed and frustrating to use, with no real control.

In many devices some menus do not even show, like some smaller tablets and then when you try to get out of this header builder / clone the feature sets and use something else better it’s no simple task to make it work and look the same.

Please advise on this and thank you…