Ben Lesh

> Stopping/starting the underlying resource would be separate from the observable, e.g. element.remove() to stop it from possibly creating events, or similar. This would mean that `button.when('click')` would, at time...

I've started a new discussion specifically about the idea of ref-counted observables here: https://github.com/WICG/observable/issues/178#issue-2559341348

> don't cancelable default-preventable events have a legitimate use case that's accepted? Off the top of my head, I feel like the most common case for this is form submit...

@kwonoj ... I think the issue is that TypeScript is not honoring line 321 there. It needs to be added to the signature.

Yup, I see the issue now. Adding a proposed change to the OP.

@staltz is right, but we do need some sort of idiom. Really it's that the _Producer_ is "hot". And the producer could live outside of the Observable. e.g. this is...

... even a "published" observable falls under that. It's "hot" because the Observable that was published is still active. The "published observable" just connects your Observer to the active source...

This type exists in RxJS-land as the result of `share()`. The only two issues I can think of, off the top of my head, that will come up with this...

I'm almost completely sold on the ref-counted observable after some deep thought and experimentation. But it does limit the type quite a bit in a few ways. A very, very...

> In what way is it configurable? I read this as: you can configure the Observable to sometimes make teardown happen immediately / synchronously, and other times delayed by, say,...