Started with a prerelease version of 2 for a greenfield project for the company I was at. Absolutely loved it. I still use it 10 years later for personal projects and am blown away at how far it’s come.

Ah, nvm, I see why I was reading it wrong. It’s the baseline widely available dates that always throw me off.

Looks like the years are off?

Yes, both for my day job and my own personal site. The style() function is useful, but I've honestly gotten the most use out of container query units. I used them for responsive text on my personal site and I think the results are pretty good!

I've never needed a GIF for a reply so fast. #tastinghistory

Bandlöscheranpassungangst.

He needs a rogue friend that’s a raccoon.

I’ve always loved this piece/character of yours. You should definitely do something larger with it.

@billcorbett.bsky.social see, I just imagine you wailing “Norman, the loons!” In a situation like this.

Ok, let's start this screenplay...

*rolls dice, checks table*
Ok, a tennis movie... might be kinda boring, but we'll see...

*rolls dice, checks table*
ooo, but with a steamy, scandalous love triangle!

*rolls dice, checks table*
and a soundtrack by Reznor and Ross?

... this should be interesting

Depends on what you’re building for the web.

Great news! I’ve already got a few components in mind I can update to use this.

They must have accidentally set validation to Australian dollars.

The snack wall against which all other snack walls are judged.

Back on Huntington ave, where the only place to have a conversation without disturbing anyone else was the cramped break room in the back. Good times!

Animating to height: auto just feels so weird after being conditioned for over a decade to think "no, you can't do that".

Quick side note here, I’ve actually published this tool to beta.worksheet.tools/wordsearch/v1

It’s easy, @scottykaye.com, all you need to do is stay up until three in the morning and ignore all your weekend chores.

Obviously, it's still a work in progress. One thing to fix became 10. But I think it's polished enough to share now.

This was also a great way to get back into the Angular ecosystem after years of working with React on the job. It's great to be back, and I'm loving building with it. Signals are 🔥.

I'm excited to be launching a tool today that I've been tinkering on for a while now. My daughter is learning to read, and I thought a tool to build word searches for her would be a fun build. It was a blast.

Check it out at beta.worksheet.tools/wordsearch/v1!

#webdev #css #angular #wordnerds

But what about <canvas>?

I think it’s whatever the hell those annoying know-it-alls are droning on about in that morning meeting.

@layer has been great when I've used it elsewhere, and I'd like to use it at my company. But until toolchains fully support it (they should), it'll be tough to convince developers to spend the time implementing it.

Something else in the library was interfering with how that plugin was being run and styles added. Too bad. But I ran out of time to investigate and had to move on to another task.

Unfortunately the library we're using handles all the style management, and I couldn't (quickly) find a way to change how it adds everything.

Emotion.js is under the hood. I was able to build a rudimentary plugin to wrap the styles with @layer, but only some appended styles were affected.

This feature that I've always wanted, and still want too, out of browser web tools is "why is this element this size?"

Is it intrinsically sized? If so, what content is affecting it? Is it directly sized? Which selectors/properties? Is the context sizing it? Tell me more!

Hooooooooot modules…

I haven’t looked at any LinkedIn Learning course for a while, but I see now they can launch a corresponding GitHub codespace now. That’s actually a really nice QoL improvement.

I've tried integrating them into our CSS stack, but keep running into blockers.

During my latest attempt, I found the CSS-in-JS solution from our third-party component library is effectively incompatible. I burned a lot of time writing plugin that would wrap its CSS output in a layer to no avail.

How about ‘text-wrap: avoid-singles’? Linguistically it’s about as neutral and simple as I could think of.