Based on the information provided in the knowledge sources, I don't have enough specific details about Ory Elements and its behavior with OIDC submissions across different browsers. However, I can provide some general insights about CSRF protection and OIDC in Ory that might be relevant to your issue: 1. CSRF Protection: Ory implements CSRF protection for all flows, including login and registration. When submitting a flow, you must send both the CSRF token in the body and the CSRF cookie [Ory Docs - Debug](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-basic-integration#debug). 2. OIDC Submission: For OIDC (OpenID Connect) login flows, the request typically includes both the

csrf_token

and the

provider

fields [Ory API Reference](https://www.ory.sh/docs/reference/api). 3. Browser Behavior: Different browsers may handle cookies and form submissions slightly differently, which could explain the discrepancy you're seeing between browser profiles. To troubleshoot this issue, you could: 1. Ensure that your implementation correctly includes both the

csrf_token

and

provider

fields when submitting the OIDC login flow. 2. Check if there are any browser extensions or settings in the profile where only the

csrf_token

is sent that might be interfering with the form submission. 3. Verify that cookies are being properly set and sent in both browser profiles. If the issue persists, you may want to reach out to Ory support or check their community forums for more specific guidance on Ory Elements and OIDC submissions across different browsers.