So, could this thread be summarized as recommending two essentially independent 
projects for "components" in Elm:

1. Make sure the virtual DOM works "sensibly" with elements with hidden local 
state.

2. Provide a standard approach to building new web components using Elm.

Those two things would probably mitigate most of the issues. One would lose 
some opportunities for type checking as data was forced across a JavaScript 
boundary, but it would mean that you could use extended UI toolkits created 
with web components and you could extend such UI toolkits using Elm.

Mark

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to