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
I think a comparison with BEM would be really great in the FAQ. A why of csstyle.
The biggest change I've noticed is the modifier, and I think there's some potential for issues where components overlap. See: https://en.bem.info/faq/#why-include-the-block-name-in-names-of-modifier-and-element particularly the part about ambiguity of what a modifier belongs to[1]. and potential for modifier overlap. I was interested in your considerations & solutions around this sort of problem?
[1] For clarity, I mean this line:
This kind of HTML markup leaves it unclear as to whether the modifier relates to the menu item (menu__item.active) or the button (button.active). Specifying the block name (button_active) indicates the BEM entity to which the modifier will be applied.
The text was updated successfully, but these errors were encountered:
I think a comparison with BEM would be really great in the FAQ. A why of csstyle.
The biggest change I've noticed is the modifier, and I think there's some potential for issues where components overlap. See: https://en.bem.info/faq/#why-include-the-block-name-in-names-of-modifier-and-element particularly the part about ambiguity of what a modifier belongs to[1]. and potential for modifier overlap. I was interested in your considerations & solutions around this sort of problem?
[1] For clarity, I mean this line:
The text was updated successfully, but these errors were encountered: