yeah i teach it, so should have it in my vocab :) i blame my allergies today.
Posts by Mia (online)
oh right, there's a way to do it directly now. perfect
Not at all computer, but ai imagine anything which triggers block formatting context on the paragraph might help. containers just one option for that. overflow:hidden is another.
🚨 delete your bsky app passwords NOW
you can always generate new ones
settings ➡️ privacy & security
also turn on 2FA
high suspicion for leaked app passwords driving the mahm*** spam network acquiring larger existing accounts, and deleting all their posts
Sometimes I'm tracking down a questions in the CSS spec, and I land on containing blocks, with my favorite line of spec poetry:
"Notably, a containing block is not a box (it is a rectangle)"
Yes. That's the sort of distinction I'm here for.
drafts.csswg.org/css-display-...
This should be illegal.
Thanks friend – I've spent a lot of time working these ideas in my head, and it's good to know they land with (at least some) other people. :)
Enjoyed chatting with PodRocket yesterday about #CSS and #Sass, and how *understanding* the language isn't required to make the background pink – but it will dramatically improve your organizing & debugging.
(And the best approach is usually to do less!)
A demonstration of the same gradient defined as a light blue to fuschia gradient, with 5 different color interpolation methods. From left to right, srgb, which kind of muddies the blended colours in the middle to a light pastel purple, lch, which moves seems to move to the blue colour quicker, not creating the purple muddiness, oklch, which does move through the purple but in a more subtle way, oklab, which remains more pink than anything, and hsl, which adds a very dark almost internet blue at the centre of the gradient
we don't talk enough about how cool the color-interpolation-method is in CSS gradients
all of these slices have the same gradient:
linear-gradient(#00ffff 0%, #ff00ff 100%)
each one is just using a different colour interpolation
Example CSS Grid layout with gap decorations. Decoration ends that form intersections are circled and labeled "Intersecting?"; decoration ends that don't form intersections are circled and labeled "Dangling?".
NAMING HELP NEEDED: Looking for single words, to be used in CSS property names, that distinguish between gap decoration ends that form intersections vs. those that don't. Best idea I've come across so far is "intersecting" and "dangling". Do you have other suggestions?
could be
but then not so fun as a premise, and if we're grounded in reality I have entirely different concerns. sentience is not near the top of my list.
the term has been used, but not at this level of cultural saturation.
It would be really funny if someone did suddenly (this is sci fi) make a sentient machine, but not using any technology even remotely like current LLMs, and then they don't know what to call it because – I'm told it's too late now – "AI" already means this thing where we predict plausible text.
Take note, car freaks, here's one simple trick to cutting your traffic by 18%
oh in that article, i agree that name-only queries are very cool! i'm responding also to some of the other discussions i've seen - some linked in replies
or even just scope ([data-bo-beta])
You have more in common with the people of Iran than you do with anyone in this administration, any member of the technocracy, anyone who is profiting from this war, or any billionaire. When you see Iranians forming human chains outside key infrastructure sites, you should feel a sense of kinship.
Note that you are allowed to make up arbitrary unique names as attributes – just like vue does –and then at-scope to them! :) It's still a shorter way to write the same thing.
But you don't have to re-name things. You're able to scope without that. And I think that's really nice.
If any conferences are interested in a talk about how to use scope, hit me up!
It's the right tool for the job in a lot of situations, and there are good reasons it doesn't do everything you might imagine under the "scoping" umbrella.
The fun in working on long-requested features like cqs or scope, is that there's no way to live up to the theoretical brilliance of CSS that will solve everything. Especially when everyone imagines something slightly different.
These features aren't revolutionary. They're merely useful.
I think something like `all:revert-layer` is the right model, but the wrong feature. We need something more like `all: from-container(<name>)`
You want the scoped styles to *not inherit* into the donut hole… but then properties inside still need a default. So to me that's a distinct question: it's less about keeping styles in the scope, more about declaring where nested elements *should* inherit from instead.
"you can't concisely indicate where it ends" Can you say more about that in relation to at-scope?
Name-only container queries are excellent, and this can be a great use-case. But the only thing that does is move scoping (and naming) into CSS properties. Useful sometimes! But it doesn't otherwise solve this problem any more elegantly than at-scope.
Compare that to:
@ container ds-card { .title {} }
"That's it, that's the scoping power we want." But… it's the same thing, less tailored to the task? And for some reason the other approach is "disappointing"?
I don't get it.
What you say you want is
ds-card { .title { } }
… But without specificity. That's what scope does by default! Here you go:
@ scope (ds-card) { .title { } }
No specificity added! And a few "niche" bonus features along for the ride.
I still find your take confusing. "That's what we didn't get with scope" – and yet… at-scope is designed to achieve *exactly* the same thing as vue scoped styles. Just a bit wordier, because you are doing it by hand.
There must be some fundamental disconnect in how we understand these things.
In which I continue to be mad about borders and prisons, while making #pottery.
Fuck the borders, burn the prisons
(enjoy some tea or coffee)
art.miriamsuzanne.com/product/burn...
A gas fireplace with multi-layered mantle, covered in books and paintings, nicknacks, and a range of my pottery scattered. on one corner, a couple vases with fake foliage, salt and pepper shaker, and lidded jar sit framed by the brick wall. At the bottom, a step stool.
My angular pottery: a vase, soap dispenser, salt n pepper shakers, and a lidded jar – framed against a brick wall.
The best photo spot in our house requires a step stool, but I think the results are pretty good.