This message was deleted.

Hey @curved-oxygen-35290 Yes, it would be good to have the ability to support a wider variety of frameworks and markup and I think the goal for us is to make elements the go to place when integrating with Ory. It took a lot of work to build everything from the ground up using a trusted technology (React) so I am a bit hesitant to just switch everything over without a proper design document and prototype of what is possible. Even then I would do a slow migration and still keep the current support in-tact as elements is used inside the Account Experience. Breaking anything in elements would mean breaking a lot more than just the library 😉 Why don't you open an issue so we can in more depth discuss the possibilities?

will do. One of the exciting things with web components is that a project can be migrated piece by piece , so that a react component could be converted, but still used withing the existing react framework. So it's not a matter of replacing a component, we could write one in webcomponents in parallel and slowly build up the library without having to do a complete rip and replace

the problem of web components is that they can only ever work with client side scripting, without scripting the browser wont know what to do with

<username-input>

for example

oh. Doesn't ory/elements have scripting then ? I thought they were react components.

tbh i’ve not dug in to it, but i would hope that while there may be some scripting that it would also be rendering standard html with a regular form that could be submitting without javascript