Andy Earnshaw

@flackr thanks for your suggestion! I'm actually using a different hack in the latest version: two scrollbars via nested containers, the inner scrollbar is hidden and always resets to middle....

Is there anything I can do to help confirm this?

It's missing all the lifecycle callbacks too. It makes it tricky to derive custom element constructors without some workarounds. ```typescript function derive(ctor: CustomElementConstructor) { static get observedAttributes() { return [...super.observedAttributes...

> ```yaml > # Custom sensor to expose the Matter pairing code to Home Assistant > sensor: > - platform: custom > lambda: |- > auto matter_pairing_code = new MatterPairingCodeSensor();...

Do you mean if they add the same callback function *or* if they bind to the "deferred phase" for the same event? I presume it's the latter, but just in...

Yeah, I understand that, I probably should have made it clearer from the start that the proposal is not looking for such guarantees. This is really just a proposal for...

After running into the problem I described, I came back here but realised that my original proposal wasn't particularly eloquent. So, I've tried to make this more of a discussion...

@thirstyfish: thanks for the workaround.

@bathos that was my first thought too and I think that would be an important blocker for this idea. I don't see how it can be reliably transpiled either, without...

Indeed, the variable-style desugaring was an oversimplification. The implementation details would be left up to the vendor. The runtime implications do make it more difficult to transpile without a WeakMap...