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

@matthewp I have seen a fair amount of components. This technique is not used as much as you might think. I agree with you that they all should have used it, but alas.  

For such a common use-case I think the standard is exactly the right place to offer some guidance in here. 
Might be in the form of a few samples, or wording that favor one option over other with s simple explanation why it would be beneficiary to everyone if we all used the same way. 

As  custom-element seem on the up in acceptance, I think now is a good time to act on this subject.

(disclaimer I'm working on an angular 1 <--> custom elements/polymer interop. In that role I found that this is something _really  missing_.)

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