Re: [w3c/webcomponents] missing guidance on implementing an 'refresh' option. (#562)

@andyearnshaw I'm a active community member, and I see something going the wrong way. 
I really like custom-elements. If this is taken care of, the interchangeability of custom-components will be better for everyone. Then you can truly mix and match components off different frameworks. If you look around, you can already see different way's this stuff is handled. 
>From my standpoint the spec is missing a 'refresh your view, reevaluate data' hook/callback/whatever.   Adding this will help. If that's not feasible providing some samples/guidance docs should be there.

Left alone, we will miss out on a opportunity to make custom-elements even more versatile as they are already are now.  

I think I have brought in all I have to give on this point, so unless directly asked, I will refrain myself from posting to this thread. I think I already sound like a broken record ;) I;m sorry about that, but I tend to be overly passionate on stuff like this ;) 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/562#issuecomment-245243614