-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
fixed-select-option-using-label-issue #5098
Conversation
@Prateek93a Can the nested label input approach be used here instead? I want to keep the |
@limzykenneth Yes, I will update the PR. |
@limzykenneth I have updated the code to use the nested label input approach. For this, I have also made small updates to the unit tests to work according to the changes. |
@limzykenneth if this looks good to you, please feel free to merge |
This looks good to me and can be merged though I only just noticed that |
@limzykenneth Sure. I will make the changes and update the PR soon. |
@limzykenneth I have made the changes. I have also added some unit tests for |
Sorry this took way too long, it slipped through the cracks. I'll review this today. |
Seems to all work fine. We can revisit if specific problems occur. Thanks @Prateek93a! |
No problem! |
Resolves #4854
Changes:
I am using the
id
attribute of the option element to set thefor
attribute of label element.I wanted to make minimal changes to the code for fixing the issue. Hence I went with approach that @dipamsen suggested. However if required I will update the code to implement the approach @limzykenneth suggested.
GIF of the change:
PR Checklist
npm run lint
passes