Conduitry

I've considered this before - what should happen with this when compiling for SSR? There's nowhere in the current `.render()` response where we could say what classes are on ``.

Anything that involves listening to all events on a DOM element isn't practical. There was a conversation in Discord between @mindrones and me about this on December 6, 2018, that...

Oh that's interesting. So we wouldn't be forwarding all of them, just the ones that consumers of the component are trying to listen to. I don't see any technical DOM...

Monkey patching `Component.prototype.fire` only helped with listening to all events on a _component_, not on a DOM element. There are a few different things going on here: - `` -...

I just realized that `` where the component contains `` would have to have caveats about not being able to report proxied DOM events from that element. So I'm withdrawing...

I'm not wild about adding huge amounts of text to the repo to test this. Can the tests be written so that the large amounts of text that are parsed...

This can't be merged in its current form, so whether it should be closed is going to depend on how strongly you feel about this, and whether you feel like...

Yup, looking at #4179 where this code was originally added, this sounds like a reasonable suggestion. Are there other text-like input `type`s we should also be handling? Or, would it...

I don't have easy access to Safari to test this, but this should be fixed in 3.44.3 thanks to @skippednote

The additional `input.value !== /*foo*/ ctx[0]` condition that I would have expected to see in 3.44.3 isn't present, which means that the change to handle `type=search` (and others) the same...