Remix: submission fails only in Chrome

[dvnrsn]

This is super random and I am not sure what to make of it or where to put it

    const submission = parseWithZod(formData, {schema: formSchema});

    if (submission.status !== 'success') {
      return submission.reply();
    }

I see that we fail submission.status !== success and return submission.reply() but only in Chrome (we've tested incognito and vice versa)

The value of submission.reply()

{
  status: undefined,
  intent: { type: 'validate', payload: { name: 'email' } },
  initialValue: {
    email: '[email protected]',
    form_type: 'inline-form',
    full_name: 'Gibberish Gibero',
    list_id: 'Ifj2'
  },
  error: undefined,
  state: { validated: { full_name: true, email: true } }
}

The result is that the browser redirects to the action route itself resulting in the display of JSON.

When I console submission itself I see

{
  status: undefined,
  payload: {
    list_id: 'XzfCUy',
    form_type: 'inline-form',
    full_name: 'Giberish',
    email: '[email protected]'
  },
  error: {},
  reply: [Function: reply]
}

[dvnrsn]

I believe this is a double submit as I see two POSTs in the dev tools but only in Chrome.

Note that if I remove {...getFormProps(form)} the submission works as expected

[dvnrsn]

Good thought, thanks. Sadly this is all we get (notice the double POST), even with the console in the onSubmit callback.

I'll have to try moving to another route or something if we come back to this.

[edmundhung]

Can you show me the payload of the two POST requests? I am wondering if this is related to #524 which seems to happens on chromium based browser only

[dvnrsn]

Certainly. Here is the first form data payload

full_name: devin
email: [email protected]
__state__: {"validated":{"full_name":true}}

And second:

full_name: devin
email: [email protected]
__state__: {"validated":{"full_name":true}}
__intent__: {"type":"validate","payload":{"name":"email"}}

edit:
What I would expect is one of the following.

{"validated":{"full_name":true,"email":true}}

__state__: {"validated":{}}

This is what we see in the cases that it works.

FWIW I don't think we're in a Dialog and removing shouldValidate: 'onBlur' (i.e., going to onSubmit) does seem to help

[edmundhung]

I think the issue you had is likely fixed on v1.0.6.

[dvnrsn]

Sadly it doesn't seem like this helps

    "@conform-to/react": "^1.0.6",
    "@conform-to/zod": "^1.0.6",

I did notice that once it works it works until I hard refresh and use new email. This immediately triggers the undesired redirect (still only in Chrome)

[deadcoder0904]

@dvnrsn do you think my issue & yours is related? i can't get 1st failure error in ui even if its shown in console.

[dvnrsn]

There are two things I'm observing that seem very similar.

1. submitting the form via return key correctly triggers the UI change in Firefox but not in Chrome (unless incognito strangely)
2. commenting out shouldValidate: 'onBlur' seems to help

Can you confirm either of these?