The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: SainathPoojary <[email protected]>
Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: hbhalodia <[email protected]>
Co-authored-by: carolinan <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Hey @Mamaduka,

I’ve moved the logic to TextControl, and it’s now working for all cases.

I’ve moved the logic to TextControl, and it’s now working for all cases.

The form provides onSumbit logic out of the box. I think the component should be using it since it's already wrapped in a form. We just need to debug. Why is it not working when scheduling inputs are rendered?

Moving logic to TextControl doesn't fix the root cause of the issue.

Hey @Mamaduka,

I tried to find the root cause and discovered that this issue occurs because the onSubmit event, triggered by pressing Enter, only works when there is a single input field. However, when there are multiple input fields, it doesn’t trigger the onSubmit event. Below is a demonstration using simple HTML

An alternative approach on triggering onSubmit would be to trigger onSubmit when Enter is pressed on the Password TextControl.

<form
  onSubmit={ ( event ) => {
      event.preventDefault();
      onClose();
  } }
>
<TextControl
  ...
  onKeyDown={(event) => {
    if (event.key === "Enter") {
      event.preventDefault();
      event.target.form.dispatchEvent(
        new CustomEvent("submit", {
          bubbles: true,
          cancelable: true,
        })
      );
    }
  }}
/>;

Please Let me know your thoughts.

Excellent detective work, @SainathPoojary!

In that case, I think going with the first approach (a4f23f9) makes more sense. Why?

• We're not modifying expected form behavior when there are two or more input fields.
• The new onSubmit callback will prevent actual form submissions from reloading the page, when only the password field is displayed.