Dane Hillard

[This research](https://github.com/supertokens/supertokens-auth-react/issues/22#issuecomment-731581119) suggests that adding the appropriate `autocomplete` attributes will give some compatibility, with hopefully growing compatibility moving forward.

Thanks for the detailed tactic suggestions @adamdehaven! We'll take them under advisement. Because we're using [Lit](https://lit.dev/) here I'm less sure of our faculties for a teleport/portal-esque approach; we'd potentially need...

> Ah. I suggested React only because I saw it in your dependency tree. We do provide light wrappers around the web components so that React plays a bit more...

@michaelwarren1106 That's an interesting tactic! I'd hope there are still `input` and `change` events fired appropriately for the inputs that get autofilled, but I've honestly not worked enough with it...

@michael-iden I much prefer to close issues as a fix for them is merged, regardless of whether that fix has yet been released—it becomes difficult to do bookkeeping otherwise.

In case anyone wants to integrate this kind of thing directly into their application, here's an example of a command I created for our Typer application to get the full...

[`custom-element-react-wrappers`](https://www.npmjs.com/package/custom-element-react-wrappers) is another alternative if it proves useful/necessary

I saw that as well and shared around internally @Niznikr, exciting development! Thanks for sharing 😄

Closing this as an unlikely area of investment going forward; we will likely divest from React wrappers instead as teams eventually move up to React 19.

@satya-achanta-venkata I have tried that but it creates a conflict somewhere that interferes with icons in particular, likely because they're dynamic modules. It needs deeper investigation.