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

auro-form talk about pros/cons of adding name attribute requirement notice to each element vs just form #211

Closed
DukeFerdinand opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
auro-form not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature

Comments

@DukeFerdinand
Copy link

Is your feature request related to a problem? Please describe.

auro-form requires the name attribute to assign values to JSON keys, where should we document this?

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Exit criteria

No response

@DukeFerdinand DukeFerdinand added auro-form not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature labels Jan 15, 2025
@DukeFerdinand DukeFerdinand changed the title auro-form talk about pros/cons of adding name attibute requirement notice to each element vs just form auro-form talk about pros/cons of adding name attribute requirement notice to each element vs just form Jan 15, 2025
@DukeFerdinand
Copy link
Author

Talked about this, decided on requiring name since HTML5 forms require the name attribute when submitting a default form. If name is not included in a JS-free HTML form, the input isn't included in FormData, so we're ignoring forms without a name as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auro-form not-reviewed Issue has not been reviewed by Auro team members Type: Feature New Feature
Projects
None yet
Development

No branches or pull requests

2 participants