On Tue, Feb 12, 2013 at 9:13 AM, Anne van Kesteren <[email protected]> wrote:
> On Tue, Feb 12, 2013 at 5:06 PM, Dimitri Glazkov <[email protected]> > wrote: > > By the wrongness, do you mean the running shadow tree instantiation and > > element finalization steps? If so, they are workarounds for our > inability to > > define an author-defined constructor. > > Yes. > > > > There's a nice thread that tries to enable this and eliminate these extra > > steps, but from what I understand, there's a monkey wrench thrown by > > inability of current JS engines to accommodate the proposed design: > > > http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/thread.html#msg250 > > Given all the other plumbing that's required to get web components > working and ES6 requires said design to work, I'd think that waiting a > little longer to do the right thing is acceptable. > "Waiting a little bit longer" is a fine phrase, except it neither sets the timeline nor priorities. If it's weeks, not months, I agree. Otherwise, I would rather consider workable solutions. We've been waiting for XBL2 for "a little bit" now :) :DG<
