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

@domenic  That's not entirely what I'm proposing. I don't even like the idea of a set-in-stone One Way.
But more like a opt-in option. Like all life-cycle hooks are opt-in. They are provided, and some elements need all of them, while others don't. 

As i said before, just a few samples on how this can be done, along with some guidance text would come a long way. 

Actually there is no need for any technical change in this. All that is needed is already in the standard. The only problem is, is that without any guidance, all custom-component builders will create a different solution for this. The consequence is that there is no uniformity between any web-components from different builders. This will create new silos of non-interoperabele frameworks. No uniform way of setting data from one component to the next will hurt the acceptance of custom-elements.

I firmly believe that that fact is something that should get some attention.


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