You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
When I have
a
andbutton
tags inside amenu-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 themenu-list
, with the current styling the dropdown styles are completely broken if I usea
orbutton
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 toa
andbutton
).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
.The text was updated successfully, but these errors were encountered: