Steps to reproduce:
- Go to the hosted live-widget demo.
- Add the feature flag
- Replace the
clientIdwith your instances values.
- Inspect Console.
- Enter valid email into widget.
- You should get the following CORS error for the
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://email@example.com. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
When I embed the Angular example, and add my domain as a trusted orgin, I still get this issue.
As far as I can tell this is a bug, but it’s very possible I’ve missed something.
Any eyes on this would be greatly appreciated as I am currently developing a solution that relies on this functionality, Thanks for your time!