Sep 2
Allow us to add Custom CSS Class for EACH header builder element
Currently some elements don't allow us to assign a Custom CSS Class, e.g. :
- WPML Flag
- Account
- Menu
- Logo
- ...
Pending
Jan 7, 2024
John Morgan: You're right, tough the reason I ask this is because I prefer to use custom classes so that my customizations don't get impacted (over time) by changes done in classes name by the support team. Few releases ago (v5 I think), WoodMart changes hundreds of classes name and I had to start spending days and days trying to fix everything after updating to that release. So by using only custom classes, I know what is what and they'll never be impacted by changes done by support team release after release.
Jan 9, 2024
Jeriss Cloud Center: As far as I remember, the following changes were made necessary to shorten the CSS selectors from ".woodmart-" to ".wd-" so ".woodmart-logo" became ".wd-logo". Don't see why ".wd-logo" or ".wd-header-my-account" can become anything else again, since all changes to shorten CSS selectors were already done. But even if they become, such signs like "PHP Time/Memory Limit", or "PHP Max Input Vars" are not empty words for WordPress users. Devs just can't add inputs and controls all over the place, especially if they are now widely used, since each of the new inputs is increasing server system requirements and cutting off users creating simple store\blog sites with cheap and affordable servers.
Jan 9, 2024
John Morgan: yes but still releases after releases, classes do change and it's not ok for me to keep looking and fixing classes name after every release. Even if now there are less changes than before, there are still some.
I can see why this might be useful for a menu element because there might be several on a page, but why add unique classes to elements that occur only once in the header, to which you can add CSS by choosing their main class (".wd-logo" for example).