In my case it was javascript. I used the html layout the plugin provides to make menus open/close when their header is clicked. Because the header is separate from the menu, I had to do some traversal of the DOM to find the menu (selecting the header, then finding the next element with the appropriate class). When another element was introduced between the header and the menu, I had to adjust; when the menu was wrapped in a container element, I had to adjust again.
One thing that would be really helpful on this would be the ability to add user-specified classes to headers and menus, e.g. a “header class” field and a “menu class” field (same for all of the related elements, such as the filter that was added). That would make customization and javascript manipulation much easier, and largely futureproof, because we wouldn’t have to rely on DOM traversal to select elements. I could give my dinner header the “menu-header-dinner” class and my dinner menu ul the “menu-body-dinner” class. That way when I click the menu header, I can use string manipulation to pull “menu-header-xxx” out of the header element’s classes and search the DOM for the class “menu-body-xxx”. Future updates to the html structure wouldn’t affect the script’s functionality.
