"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.

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?

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

And jquery! And ES5!