-
Notifications
You must be signed in to change notification settings - Fork 86
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
fix: add hidden input with name attribute #2212
Conversation
✅ Deploy Preview for marvelous-moxie-a6e2fe ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Co-authored-by: felix-ico <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you decide to use a prop with a different name, adding it to Storybook would be necessary imo.
@@ -208,6 +208,8 @@ export class DropdownSelect { | |||
@Prop() ariaLabelSelected?: string = 'selected'; | |||
/** (optional) Text displayed in high contrast mode only to indicate disabled state */ | |||
@Prop() hcmLabelDisabled?: string = 'this field is disabled'; | |||
/** (optional) is the element used in a form */ | |||
@Prop() formAssociated?: boolean = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't call this formAssociated
because it's not exactly the same as the standard static method.
I would actually not use any prop at all and just render the hidden input, always. The button has similar "hacks"… What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense, will do that instead
this should fix #2173