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

BEM Comparison #59

Open
SevereOverfl0w opened this issue Nov 6, 2015 · 1 comment
Open

BEM Comparison #59

SevereOverfl0w opened this issue Nov 6, 2015 · 1 comment

Comments

@SevereOverfl0w
Copy link

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.

@geddski
Copy link
Owner

geddski commented Jul 29, 2016

usually you'd only apply one component to an element at time, so the modifiers aren't vague. I can see it being confusing though if you use multiple.

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

2 participants