Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

menu-list class should not influence a and button tags #3971

Open
leonardo-panseri opened this issue Mar 4, 2025 · 0 comments
Open

menu-list class should not influence a and button tags #3971

leonardo-panseri opened this issue Mar 4, 2025 · 0 comments

Comments

@leonardo-panseri
Copy link

When I have a and button tags inside a menu-list class, they are styled with the .menu-list a,.menu-list button,.menu-list .menu-item and the respective variants for :hover, :active, .is-active, .is-selected.

This is undesirable because it makes it really difficult to have other elements/components inside a menu list. A very common example would be a dropdown for each element of the menu-list, with the current styling the dropdown styles are completely broken if I use a or button inside it, and it is not trivial to fix this with custom CSS, since the styles for these tags are reset and overridden with a high specificity.

I think the better approach would be what Bulma is already doing for almost every other element/component: let the designer decide if they want the styles or not with a class (in this case there is already the menu-item class that applies exactly the same styles that are applied by default to a and button).

For now I am forced to vendor my own version of Bulma just to remove all .menu-list a,.menu-list button selectors, leaving only .menu-list .menu-item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant