On Tue, Apr 16, 2013 at 10:33 PM, Dimitri Glazkov <[email protected]> wrote:
> On Mon, Apr 15, 2013 at 6:59 AM, Anne van Kesteren <[email protected]> wrote:
>> The other problem we need to solve is that document.createElement(<x>)
>> currently gives different results from new <x's interface>. E.g. new
>> Audio() sets an attribute, document.createElement("audio") does not. I
>> think we should settle for document.createElement("audio") also
>> creating an attribute here.
>
> What if we use the newly-found power if readyCallback here?
>
> Suppose that HTMLAudioElement has a readyCallback that, among other things
> does:
>
> if (!this.parentNode) // aha! I am created imperatively
> this.setAttribute("controls");
I don't understand. In either new Audio() or
document.createElement("audio") there's no parentNode.
> Several HTML elements will need to use the callback to build their
> shadow trees and set internal state, like <textarea>, <input>,
> <details>, <fieldset>, etc.
It seems that too is irrespective of what way is used to create these elements.
> If we just build readyCallback into DOM, we have cake.
If this is what that callback is for, I don't see the need. The above
bits can just be part of the constructor of the element.
--
http://annevankesteren.nl/
