Matt Clough

3Quency won that show immediately. So good.

Building the Band is like Tiny Toons of pop stars

"Mock" has heavy testing associations, but it feels appropriate here too.

It kind of just sounds like... workarounds? Presumably code does this because the proposed standards can't be used yet.

I've been thinking for a while that a grim effect of the proliferation of AI across *everything* is that human work will become artisanal. Good for the humans that will do the work, still an unfortunate turn for our world though.

You're either a Equus Asinus person or an Equus Caballus person

Might fuck around and start calling people “nitwits”

It shows

The proof is in the pudding

Yeah, Cypress unfortunately

I would hope the consumer would assume responsibility for failures if they change internals, but in the case that they just want to click a button in the shadow DOM, for example, in a browser test.

Do you expose the elements via the component's API? Do you just tell them to drill into the shadow DOM?

Web component authors: how are you helping consumers run browser tests that need to interact with elements in your shadow DOM?

Woah cool

it is how we are born

being sticky and not knowing what day it is

Ah, right. Yeah, I'd assume a single one would be better for performance, but a lot of what I'm finding seems to suggest that they're pretty performant and any performance hits would be negligible (especially compared to deprecated MutationEvents, which I'm just now learning about)

In the first case, are you just observing the document? I think any observed element can be garbage collected once it's removed from the DOM. Answer aside, I'm curious what you're using the mutation observer for.

Neither of those have ever been deal-breakers in my experience. At least in Baltimore.

I’ve spent almost 3 days of my life on this lawn mower

Mowing music: Beethoven’s 9th

Would love if live NodeLists were watchable

The Doncarlo Icognito arc is a masterpiece

And jquery! And ES5!

I built an e-commerce site in like 2015 that had a streaming video player that featured product callout overlays, and a CMS for uploading those videos and tagging those products. That was about a year into my career and I learned so damned much so quickly. It was built in angular. Angular.

Emmet!

I was laid-off and am looking for a new role.

Working were design meets code is my jam. I am skilled at building accessible design system components, working with Web Components APIs, and creating scalable CSS architecture.

I work remotely from my home in Manitoba, Canada. 🇨🇦

Shares appreciated!

Do yall do slot controls in your design system Storybooks? I provide them, but you still have to provide the `slot` attribute on any markup you put in the control, which kinda just feels pointless, beyond showing that the slot exists.

As convinced as anyone can be that there is some good in consumer-facing AI, I don't think many people would agree that we are better off as individuals or as a world thanks to the kind of big tech companies that are now pushing AI. I feel like we need to just remember that and reject this crap.

Who's keeping the word "teetotaler" around and why do journalists love it so much?