nzdeep

Perhaps I'm misunderstanding, but as I understand in this scenario then, shouldn't e.currentTarget be document? Currently it looks like currentTarget is faked to the button? (https://developer.mozilla.org/en-US/docs/Web/API/Event/currentTarget)

Highlighting more problems https://playground.solidjs.com/anonymous/6cb3e2a0-7eea-402a-9a7b-baf6d84d4b49 This is smallest reproducible examples I can do, but make no mistake this perpetuates across everything to bigger issues

I'm working around it at the moment by using the deepest path to extract values, but honestly we've got part of the app that at least I've lost complete confidence...

 This will pull the latest on the playground I believe, but in our setup we're using 0.19.1 right now as upgrading was first attempted, but same result in 0.17

We dont render via Field all properties, but yes it is the same _dangerous_ story https://playground.solidjs.com/anonymous/f71bc588-9a66-4185-b30e-0ef9ee8e2a50

Okay, different approach there, we probably need an interim warning that every field needs to bound (regardless of shouldactive) and nested arrays that binding needs to happen via FieldArray (as...

For the first bug: 1) Click the 1st button and observe the field of votes changes to dirty 2) Click the 2nd button the field remains dirty due to keepDirtyValues...