Web Component or Custom Element Support about vugu

[snoop244]

The benefit is that teams, like ours, with existing applications could start mixing in golang wasm components, particularly in areas where wasm will shine over js... without having to (re)write the whole application in wasm.

[snoop244]

Apologies for the multiple posts. Here is a somewhat dated post on golang WASM web components: https://matthewphillips.info/programming/wasm-golang-ce.html

[bradleypeabody]

Thanks for the issue. I'm not too familiar with WebComponents and the ins-and-outs of their use. Other than using a custom element in your HTML and including the appropriate JS file, what else would be needed in order to make this work?

Vugu doesn't much care what HTML elements it outputs. If you put a tag in a vugu file, Vugu will end up calling document.createElement('some-custom-element') to create the DOM for it. Although just from a quick look here https://developer.mozilla.org/en-US/docs/Web/API/Document/createElement it seems like there needs to be an options object passed with an is property as the second argument. So yeah it would seem that needs something custom from Vugu.

Is there anything else that would be needed to make this work? It sounds like it could be done without too much trouble.

[ystyle]

It now supports use web Component in vugu， but it will has some error. see this #62