I'm not aware of any of those complex reasons... when I mentioned this as a use-case to tab (on twitter) he seemed open to it.
-
-
Replying to @matthewcp
you mean
@tabatkins? decorators were the use case?2 replies 0 retweets 0 likes -
Replying to @briankardell @tabatkins
I brought up a decorator-like idea to use this sort of api, yes. I don't know what decorator baggage you are worried about though.
1 reply 0 retweets 1 like -
Replying to @matthewcp @tabatkins
just that immediately you are likely to get a lot of responses about why decorators failed rather than what you really care about :)
1 reply 0 retweets 0 likes -
Replying to @briankardell @tabatkins
I'd welcome those responses, I've searched the internet for the answer to that question but was never able to find it.
1 reply 0 retweets 0 likes -
Replying to @matthewcp @tabatkins
maybe
@slightlylate or@addyosmani can share some stuff, I am swamped :(1 reply 0 retweets 0 likes -
Replying to @briankardell @matthewcp and
It just turns out to be very messy to swap out DOM interfaces dynamically. Enough trouble with the one "upgrade" that already happens.
1 reply 0 retweets 1 like -
Replying to @tabatkins @briankardell and
We looked *very* hard at decorators in the WC design. Changing what a "thing" is almost never works out (because un-application).
1 reply 0 retweets 2 likes -
Replying to @slightlylate @tabatkins and
Where did decorators swap out a thing? I thought it was just creating a shadow and cloning a template into the shadow.
2 replies 0 retweets 0 likes -
Replying to @matthewcp @slightlylate and
And removing the shadow and putting a new one in, as selectors change. But WC are more than just shadows, you want APIs on them.
1 reply 0 retweets 2 likes
Right. Basically, you know how <input> is spawn of the devil because it's *actually* 12+ different things? That's what decorators create.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.