Re: [w3c/webcomponents] Why does attributeChangedCallback fire when a new attribute value is the same? (#676)

> it's a fault of the caller.

Maybe, but easily avoidable by the engine.

Is the reasoning to avoid implementation complexity? Or something else?

The only thing I can imagine is using the act of setting attributes as method calls (sort of like how jQuery uses strings for method calls).

```js
elm.setAttribute('doSomething', 'arg')
// ...
elm.setAttribute('doSomething', 'arg') // do it again later
```

but the custom element can also just provide an actual method.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/676#issuecomment-336523715