Ryan Weaver

Wow, this is very interesting! I would love to add another link for another demo - thanks :). I'll check out your demo - I have some comments / questions...

to make sure I understand, if you remove: ``` connect() { console.log('demo'); document.getElementById('form_oldFile').addEventListener('change', (event) => this.onChange(event)); document.getElementById('form_file').addEventListener('change', (event) => this.onChange(event)); } ``` then it works ok in safari? If so,...

Thanks - it seems like we might finally be "circling around" the problem. But it's definitely bizarre.

In many tests, we silence these, and it's something that we should do for all of them. To be clear, I don't mean that we should silence them globally. What...

Yep - we’ve never really made silencing them a priority. We should.

The `tailwind:init` command still needs work for v4 #95, but for v4, here's what you need: A) Delete `tailwind.config.js` (`content` is now automatic) B) In `app.css`: ```diff --- a/assets/styles/app.css +++...