Allow Uncontrolled Components

[vixalien]

Feature request summary

Components like TextField and Select only work when they are controlled, i.e. they need the properties value and onChange be set so that their state can be managed by javascript code.

Rationale

By allowing form inputs to be uncontrolled, we could eliminate those props and ensure Polaris Forms works without JavaScript. This is particularly important in Remix, where the browser should be delegated to do everything it can and use JS when necessary.

---

🌟 Feature requests that are not yet planned will be closed. We then use the issue’s 👍 upvotes to track and set priorities. See the contribution guidelines for more information.

[davidhousedev]

Another dimension to this is compatibility with the App Bridge components. For example, the Contextual Save Bar relies on native HTML for events and states in order to work properly, but it's challenging to emulate the required events when you're using controlled inputs.

Being able to use uncontrolled inputs would ensure that all native DOM events get sent by-default.

[mkromann]

This would be lovely — especially considering that Remix is such a breeze with uncontrolled components.

[github-actions]

Hi! We noticed there hasn’t been activity on this issue in a while. After 30 days, it will close automatically.

If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.

[vixalien]

This is still relevant…

[grundmanise]

Agree. I don't see a reason why they should be controlled components only.

[JannikWempe]

This should have a high prio after Remix has become the standard.

Remix works very well with uncontrolled components and common libraries like conform rely on them.

Adding support for uncontrolled inputs would make development a lot easier.