What posts of Chris and Jose are you referring to here?
When talking about webcomponents I think we have to first define what exactly we talk about:
- single elements that are made with LV in mind
- using a webcomponent lib like Adobe Spectrum, Adobe Carbon, Siemens IX, shoelace (will be webawesome)
(1) should be easy enough. (2) is outright impossible right now without significant hacks, the main prolems being that the components store their state in properties which LV kills. You have to know exactly what those are and catch them (doable without touching LV-js). Also libs that build their own form elements can only be used if one patches the special form handling inside the LV-js (afaik Siemens IX is the only one that augments standard form-elements and is thus the only one of the big libs that are right now usable with LV - with some hassle).
I think there has to be some LV-awareness in the webcomponent lib. For example it could come with some kind of manifest so that LV knows what not to touch, or even generate some API to manipulate client state, eg open a modal.
