- From: Joe Pea <notifications@github.com>
- Date: Tue, 24 Oct 2017 16:22:09 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 October 2017 23:22:42 UTC
> They should instead interpret the absence of an attribute as triggering the default behavior. That's true, I'll think about that, though currently I think it's cleaner to see (f.e. in the Inspector) the default values so it's easy to learn from. And it doesn't harm how anything like React/Vue/Angular works. Do you know any ways it might harm other code somewhere? Seems like well-documented elements will probably not have a problem as long as they don't morph the HTML structure because React/Vue/Angular they track the DOM structure, but not attribute references (they only use setAttribute to update DOM). Plus, builtin elements already do morph DOM, f.e. `<table>`. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/522#issuecomment-339165727
Received on Tuesday, 24 October 2017 23:22:42 UTC