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

I know its a property change. And you have shown yet another way to handle it. More diversity is just what is the problem in this case. 
What I miss is what is usually called a best practice. 
The need to refresh the view of your element after a property change is pretty universal.  There are a lot of way's to handle that. 
I think favoring one way by putting it in the webcomponents standard as the preferred way to handle such a case would help inter framework/custom elements a lot in the future.



-- 
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-245012039