Andreas Svensson

The `muted` **property** is live just like `value` for inputs and reflects the current value. But the `muted` **attribute** reflects the initial state of the component. So I think the...

@gaearon This should be an easy fix if you're OK with the direction (making `muted` set the attribute instead), although there is potential to break some existing code if someone...

> It's unclear what the path forward is for this to me. We don't really have way of saying "sync the attribute once and then use the property" and I...

@kzc Interesting, thank you! ~~I'll bring up this issue with terser instead then.~~

Oh wait, this is a bug in Babel then, isn't it. As babel actually fails when the variable is declared as e.g. `let` in both For and Statement. Which if...

@kzc Yeah bable does error on it, see below. Thank you again. https://babeljs.io/repl/#?babili=false&browsers=ie%20%3E%3D%2011&build=&builtIns=false&spec=false&loose=true&code_lz=GYewTgBAFANgpgFwgDwiYEDaBGAugSggG8AoCCeJZAXmwG4SBfIA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=true&fileSize=false&timeTravel=false&sourceType=module&lineWrap=false&presets=&prettier=false&targets=&version=7.4.5&externalPlugins=

@kzc Sorry, I unclicked everything and it still showed the error for some reason. But when I refreshed now it would no longer show. The link below reproduces it, it...

@kzc Interesting results! Although without looking at the code I would speculate that the reason it works is because `transform-for-of` incorrectly sets up the scope (or such) and it is...

#4492 related I think. Anyway, it's simply because the element emitting the event is replaced and it messes up the events. I could be wrong, but IIRC there's also some...

My perspective on this: `` (as sugar for ``) seems kind of quirky, but `` seems reasonably useful for the same reasons as `{item, key}` was added to ES6. But...