Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infinite loop caused by Address Autofill in Chrome #1857

Closed
jakobmcfarland opened this issue Dec 21, 2021 · 1 comment · Fixed by #1864
Closed

Infinite loop caused by Address Autofill in Chrome #1857

jakobmcfarland opened this issue Dec 21, 2021 · 1 comment · Fixed by #1864
Milestone

Comments

@jakobmcfarland
Copy link

Describe the bug

After upgrading to 3.0.0-alpha.3, using address autofill prompt in chrome causes a "Maximum update depth exceeded" error. This only occurs if three or more fields are autofilled at once. Firefox's equivalent address autofill seems to work as expected.

Expected behavior

The address fields should be autofilled without crashing.

Steps to reproduce the issue

  1. Add a test address in chrome://settings/addresses.
  2. Create a form containing at least three fields labeled "Name", "Address", and "City".
  3. Click on one of the fields, and the chrome autofill dialog should appear.
  4. Click on the test address.
  5. React should crash due to an infinite loop.

Screenshots

jsonforms_address_autofill_crash
jsonforms_address_autofill_crash2

In which browser are you experiencing the issue?

Google Chrome Version 96.0.4664.110

Framework

React

RendererSet

Material

Additional context

I recreated this in the jsonforms-react-seed, only changing the schema and uischema.

@sdirix
Copy link
Member

sdirix commented Dec 22, 2021

Thanks for the report. We'll take a look as soon as possible :)

@sdirix sdirix added this to the 3.0 milestone Dec 22, 2021
@sdirix sdirix linked a pull request Jan 4, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants