Viewing profile — TabAtkins

Fwiw, while I deeply appreciate WebKit supporting the proposal as well, the editors of the Nesting spec are Googlers and the Chrome impl happened at the same time.

Depending on the exact parsing strategy it might be genuinely required (such as if the parser switches from "property mode" to "rule mode" at some point), but in this case it was j…

Notably, this is identical to the behavior you get from @scope's nesting, and from passing a complex selector to an `el.querySelector()`. (We discussed adopting Sass's behavior in …

Or search engines, which are a special case of disabled users.

"Anne" is a male name in the Netherlands. (I don't know if it can also be a female name there, but this Anne is definitely male.)

The CSS 'contain' property helps ensure that local changes don't cause dirtiness to spread higher up the tree. " rel="nofollow">https://drafts.csswg.org/css-containment/> I know Ch…

> drops all resolved CSS rules on element, its siblings, its parent and all children. Browsers optimize this, too - they try hard to keep up metadata structures that tell them whet…

Saying "People have different opinions" about nazi bullshit is kindergarten-level analysis. Nazis are bad. Racists are bad. Claiming these "opinions" are equivalent to any other is…

I mean, okay, maybe, but that just means that they'd be hosting a conference about "nazis suck" and hey, I'm okay with that. That's a message I can get behind.

"Just add native support for jQuery and call it a day" "Just add native support for React and call it a day" We can do lots of amazing things in the ecosystem, but often we're work…

That's exactly what you can do. var() is replaced at computed-value time, so calling gCS().color will return "red" or whatever. If you use an API that gives you the value at an ear…

Yeah, CSSNext here is basically the intersection of CSS variables and Sass variables - you can only use them in property values (like CSS), and you can only declare them at top-lev…

If I'd done what everyone keeps saying I should have done and just used $foo, then Sass would have gotten angry at me, because we'd be sharing syntax for different features. We alr…

> He's the guy who wasted a decade writing an ASCII-art based "template layout module"[1], which he was never able to persuade a single browser vendor to implement. It eventually g…

Properly, the --foo stuff is a Custom Property. You can use its value as a variable, with var(), but it's not the only use custom properties have. That's why the spec's full name i…

lolololol obvious troll is obvious "i disagree with you, thus you must be lying about your experience and actually unworthy of doing your job, unlike me, the superior being" go get…

Yeah, setting an explicit aspect-ratio is on the roadmap. The relevant people (me and fantasai) have too many other layout-related things on our plate atm to deal with it, but it'l…

CSS selectors always select "down the tree". Or, read in reverse (from right to left), evaluating them only requires information from further up the tree. In HTML, "further up the …

Yup, that's the problem with having a language that evolved slowly over 20 years, while its problem space changed enormously. CSS was originally intended as a simple way of styling…

Both, either. ^_^ Having wrapping behavior split the way it is today is wrong - either all of it should be in white-space, or none of it should be. (Moving it all out into a separa…

Yes, that's the point. ^_^ IE's "'width' sizes the border box" behavior was the better behavior. This was very early in the CSSWG's life, tho, and the group as a whole was less mat…

As a very busy CSSWG member... I agree. There are a number of benefits to the current structure, but I highly suspect that if the web were invented today, styling would a JS-mediat…

CSS layout is about two things - the relationship between an element and its parent (and its siblings to a lesser extent). It's specified in two halves: the parent lays down genera…

I assume you mean property names, because keywords are all over the place and don't have anything to do with colons. It's just a separator between the two semantic halves of a decl…

We have variables now " rel="nofollow">https://drafts.csswg.org/css-variables/> so it's not a mistake that needs a time machine.