TabAtkins

7 ms·

1.
by TabAtkins 4y ago
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.
2.
by TabAtkins 4y ago
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 just because it's kinda confusing to
3.
by TabAtkins 4y ago
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 < https://github.com/w3c/cs
4.
by TabAtkins 10y ago
Or search engines, which are a special case of disabled users.
5.
by TabAtkins 10y ago
"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.)
6.
by TabAtkins 10y ago
The CSS 'contain' property helps ensure that local changes don't cause dirtiness to spread higher up the tree. < https://drafts.csswg.org/css-containment/> I know Chrome has an implementation that I
7.
by TabAtkins 10y ago
> 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 whether they need to invalidate styling or not. (This is w
8.
by TabAtkins 10y ago
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 childish and immature. Grow up and real
9.
by TabAtkins 10y ago
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.
10.
by TabAtkins 11y ago
"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 working around missing primitives in th
11.
by TabAtkins 11y ago
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 earlier time, like el.style.color (which is &qu
12.
by TabAtkins 11y ago
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-level (like Sass). It's nice if you really want to utilize
13.
by TabAtkins 11y ago
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 already tweaked CSS a little to avoid that in anothe
14.
by TabAtkins 11y ago
> 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 got demoted from a working draft to a &quot
15.
by TabAtkins 11y ago
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 is "CSS Custom Properties for Cascadi
16.
by TabAtkins 11y ago
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 your diaper changed
17.
by TabAtkins 11y ago
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'll show up in the next year or two.
18.
by TabAtkins 11y ago
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 tree" corresponds exactly to "earli
19.
by TabAtkins 11y ago
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 text documents on the web. We're trying to fix ve
20.
by TabAtkins 11y ago
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 separate property is probably best, so white-space can keep just
21.
by TabAtkins 11y ago
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 mature, so it didn't va
22.
by TabAtkins 11y ago
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-mediated aspect of the DOM, not something fully separate like it
23.
by TabAtkins 11y ago
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 general dictates about how its children will be laid out (v
24.
by TabAtkins 11y ago
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 declaration. It could just be a space, but it wouldn&
25.
by TabAtkins 11y ago
We have variables now < https://drafts.csswg.org/css-variables/> so it's not a mistake that needs a time machine.
26.
by TabAtkins 11y ago
trolololol The term "blend mode" is a term of art in the industry, yes. But "mode" is always redundant - lots of properties switch "modes", particularly the ones with keyword values. For example, we could have
27.
by TabAtkins 11y ago
It is, still. You want separation between your paragraphs and other elements; you don't want the first and last children of a box to be separated from the edges of that box. Margin-collapsing does that (sibling boxes collapse margins
28.
by TabAtkins 13y ago
The srcset attribute by itself can't do what you ask; it only lets you specify multiple resolutions of an image, all (intended to be) the same size. But wait for implementation to finish, and you'll be able to use the sizes='
29.
by TabAtkins 14y ago
You, um, know that Selectors is one of the few specs without naming problems, right? Its url is "selectors4". As well (partially as a result of me writing this blog post), we're looking into changing our URL structure, which was original
30.
by TabAtkins 14y ago
If there are any problems, it's because you're using an old browser. (As far as I know.) The iPhone browser definitely counts as "old". ^_^ In particular, a bunch of browsers don't support specifying background-size in the background shor

More ›