Re: [w3c/webcomponents] [idea] Ability to define Custom Element attributes (and optionally enable getters/setters for those attributes). (#517)

> IMO a better solution would be for HTML, when parsed, to take the attributes and apply them as properties.

I think I like that too, but is that backwards compatible? Current native elements don't all do that, so then we'd be adding a rule that doesn't explain existing technology properly (web manifesto) because existing elements don't follow it, and we can't change those elements to follow it because backwards compatibility.

So, what can be the backwards-compatible solution? Ability to specify certain attributes as properties/getters/setters agrees with web manifesto because then for existing native elements that don't have the properties we can just say that those elements just didn't define them as per this new API.

---
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/517#issuecomment-229289919