Live data from Hacker News

You want enabling CSS selectors, not disabling ones

css-tricks.com

1–10 of 120 posts

Re: You want enabling CSS selectors, not disabling ones

#3
This reminds of an idea in math that proofs by construction are better than proofs by contradiction. Or making artificial grammars (e.g. PLs) with recursive descent parsers instead of context-sensitive grammars with Turing-complete parsers.

If you can build something step-by-step with a clear hierarchy and easy to trace causes and effects, the result seems to be more convincing/reliable than a process involving a bunch of logical roundabouts. Of course, if that's at all possible for a problem at hand.

Re: You want enabling CSS selectors, not disabling ones

#6
I found the linked article "Axiomatic CSS and Lobotomized Owls" to be a decent read. I'm surprised that it hasn't been highly upvoted in the past despite having many submissions to HN.

Article: https://alistapart.com/article/axiomatic-css-and-lobotomized...

Prev. submissions: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

Re: You want enabling CSS selectors, not disabling ones

#9
> I think gap is where this is all headed in the long term.

gap? Is this new? I've been waiting for years for CSS to finally support something like that. Always thought it was weird that I had to mess with margins (and last-child hacks) to get a proper gap between items in a container.

Re: You want enabling CSS selectors, not disabling ones

#10
post #2

I don't see why 0 should be treated as special value. Initial should be used if meant to "disable" it. What if you want margin: 5px as the general rule and margin: 10px on the last element. Is 10px a disabling selector?

I believe that's exactly the point. You don't set all to 5px and then override using a special rule that says 0px for the last. You exclude the last element from the 5px rule.

There might be other rules, browser, user that should not over the 5px rule

Post reply on HN