You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When running sites that use Uniform through Pagspeed (https://pagespeed.web.dev), I am getting a Form elements do not have associated labels warning triggered by the honeypot field. I know it doesn't really need one as it is just a bot trap, but it would be good to have one there so this warning isn't triggered. It could simply be the name of the field.
Describe the solution you'd like
Add a label to the honeypot field input
Describe alternatives you've considered
If there is a way for me to do this myself I am happy to give that a go too
The text was updated successfully, but these errors were encountered:
Hi, sorry for being silent for so long. While you can add the label as plain HTML if you need it, the generated honeypot field does not have an id. I'd add an optional id argument to the honeypot_field() helper to make the label/input combination possible. What do you think about that?
You can reuse the uniform__potty class to hide the label. Would you open a PR with the changes to the helper method and an update to the documentation? I noticed that the documentation for the class argument is also missing so if you would, you could add this too.
Is your feature request related to a problem? Please describe.
When running sites that use Uniform through Pagspeed (https://pagespeed.web.dev), I am getting a Form elements do not have associated labels warning triggered by the honeypot field. I know it doesn't really need one as it is just a bot trap, but it would be good to have one there so this warning isn't triggered. It could simply be the name of the field.
Describe the solution you'd like
Add a label to the honeypot field input
Describe alternatives you've considered
If there is a way for me to do this myself I am happy to give that a go too
The text was updated successfully, but these errors were encountered: