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 naming convention and extends in markup. #195

Closed
Florian-R opened this issue Apr 4, 2013 · 3 comments
Closed

BEM naming convention and extends in markup. #195

Florian-R opened this issue Apr 4, 2013 · 3 comments

Comments

@Florian-R
Copy link

Not really an issue, more a question.

I totally get the point of the BEM naming convention, it's hugely useful to see how elements relate to each other.

What's unclear to me is why some objects who extends others doesn't repeat their ancestor name.

For exemple, the pagination object extends the nav object. If i remove the nav class, it breaks. Would it make sense to rename it .nav--pagination or i am missing something?

@iparr
Copy link

iparr commented Apr 4, 2013

In my opinion, in this case, if pagination doesn't work without the nav object then it should be .nav--pagination.

After-all, pagination is a type of navigation so this seems to make a lot of sense.

@leevigraham
Copy link

@csswizardry can you provide some guidance / feedback on this?

@csswizardry
Copy link
Owner

Please see #291.

Thank you.

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

4 participants