boolean attributes not observerd by default? about hyperhtml-element

[WebReflection]

so ... you want booleans then you use setAttribute ? if you els[1].active = false you'll have observed behavior through attributeCHangedCallback, otherwise you can define whatever you want through all options.

Boolean attributes are meant to be used like in <button disabled=${true || false} /> or button.disabled = true || false

[WebReflection]

also, just to be sure we are on the same page, to make boolean attributes observable you simply add the name in observedAttributes meaning it's more flexible but also more semantic.

To have what you need automatically you can simply write:

static get booleanAttributes() { return ['active']; }
static get observedAttributes() {
  return this.booleanAttributes.concat('attr1');
}

That would work better with inheritance too.

TL;DR the idea of keeping boolean a part from magic behavior was meant, which is why those are defined before observedAttributes so that there are no interferences.

In this way all possibilities are open and putting a behavior together isn't difficult at all.

The most common use case for booleans in hyperHTML/Element is to define them right away while observing has a cost and if I can avoid implicitly adding a cost for all booleans used simply to style components or communicate a state, I'm happy doing that way.

I hope it's clear why it's like this, and I'll close this for now and I'll change eventually if convinced there is a need to penalize all boolean attributes by default.

[WebReflection]

After thoughts ... is it the render() that you are missing in there ? now that might be indeed handy to trigger on boolean changes, would that work? Still I wouldn't make booleans observable by default.

[WebReflection]

Actually you know what? I think your expectations should be matched.

[WebReflection]

Sorry for the monologue-storming ... I've fixed it, if you update dependencies in your example everything should work as expected.

Please let me know if that's not the case.

[pinguxx]

seems to be working, thanks for the fix, i think this is much better, no worries about the monologue i get to see your thought process on things, it's actually very helpful