-
Notifications
You must be signed in to change notification settings - Fork 161
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
Form.formid has no effect on Field.oid autogeneration #394
Labels
Milestone
Comments
@ezag I think that is a good proposal. Would you like to submit a PR with tests? I'd accept it. Please note that we are dropping Python 2.7 and 3.4 in the next release, so you don't need to test for that. |
ezag
added a commit
to ezag/deform
that referenced
this issue
Jun 11, 2021
ezag
added a commit
to ezag/deform
that referenced
this issue
Jun 11, 2021
ezag
added a commit
to ezag/deform
that referenced
this issue
Oct 22, 2021
ezag
added a commit
to ezag/deformdemo
that referenced
this issue
Oct 22, 2021
ezag
added a commit
to ezag/deform
that referenced
this issue
Oct 22, 2021
ezag
added a commit
to ezag/deform
that referenced
this issue
Oct 22, 2021
ezag
added a commit
to ezag/deform
that referenced
this issue
Oct 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per docs,
formid
argument is intended for placing more than one Deform form into a single page. Though autogeneratedoid
s will conflict in this case (violating HTML standard and breaking JS that rely on DOM ids) unless being explicitly specified in schema, or multiple forms being initialized with a sharedcounter
. Could this be fixed by making parentformid
a part of autogeneratedoid
?The text was updated successfully, but these errors were encountered: