On 3/11/13 5:18 PM, Elliott Sprehn wrote:
"inserted" and "removed" can probably be end of micro task, but
attributeChanged definitely needs to be synchronous to model the
behavior of <input type> where changing it from X to Y has an immediate
effect on the APIs available (like stepUp).
Hmm. That's a good point. We should rope in Jonas and Olli on this bit.
As long as it's ok to call attributeChanged right before the return from
the attribute mutator, this seems to be a reasonable thing to me.
-Boris
