Re:Show HN: CSS Quality Guide
by mikewhy on Friday July 10, 2015 @01:00PM
(#9865179)
If you have say a post entry:
And you want to put it into a sidebar
That post's title is now going to be underlined. That's one of the reasons
for namespacing. If the classes were `.post--title` and `.sidebar--title`, this
would be avoided
[ Parent
| on HN ]
I had an explanation as to why your CSS was wrong but then I realized an HTML example is needed. I'm assuming you mean something like this:
<section class='content'>
<div class='post'>
<h1 class='title'></h1>
</div>
</section>
<section class='sidebar'>
<div class='post'>
<h1 class='title'></h1>
</div>
</section>
If so, what you say would indeed happen.Also, I've never thought of .post--title as a form of namespacing. I always understood it to be more like .post .title, as in nesting with SCSS or Less. Not saying you're wrong, just never thought of it that way.
Re:Show HN: CSS Quality Guide
by armandososa on Friday July 10, 2015 @02:07PM
(#9865649)
I've found that these cases are non-issues when you use something like BEM. The downside is that the HTML then becomes horrible to look at:
<div class='sidebar'>
<div class='sidebar__post'>
<h2 class='sidebar__post__title'>
Please kill me
</h2>
</div>
</div>
So… you have to chose between unmaintainable CSS or weird HTML.I think that, in the end, something like this is the only sane outcome: https://medium.com/seek-ui-engineering/the-end-of-global-css...
I probably wouldn't go so far as to use `sidebar__post__title `, just `sidebar--title` and `post--title`. That way if you want to style a post title in the sidebar, it's clearly `.sidebar .post--title`
using something like BEM solves a lot of problems. Silly collisions and searchability are my big takeaways.
Re:Show HN: CSS Quality Guide
by austinlyons on Friday July 10, 2015 @01:13PM
(#9865283)
Wouldn't you just instead write the CSS as follows?
.sidebar.title {
text-decoration: underline;
}That likely wouldn't have the intended effect as I find it doubtful that the element with the sidebar class would also be the title.
Well, you could also write .sidebar > .title to be more specific than simply all .title elements in .sidebar, but the point is to not tie your CSS quite so closely to the HTML hierarchy I suppose.
If not underlining post titles is so important, than the CSS rule should make that explicit:
.post .title { font-weight: bold; text-decoration: none; }
Leaving text-decoration out of the rule is basically saying: "I defer to my ancestor rules for advice on styling this, and I accept their decision."
It's not just that the post titles shouldn't be underlined, it's that one elements style should not creep into another elements style by accident
Re:Show HN: CSS Quality Guide
by marcosdumay on Friday July 10, 2015 @03:46PM
(#9866295)
Well, the "all descendants" selector is explicitly intended to do that. It's a bit too far to call it "by accident".
There's rarely a real use for the ".sidebar .title" construction.