Hi!, I have read that the users who have CSS disabled will see the field with the "display: none", and if we write something like "If you see this, leave this form field blank" for them the bot will read it as well and may avoid it.
I was thinking a way to avoid this problem: just hide the honeypot field with an "ap Div" layer so the user won´t see it and I think it won´t be affected by a css disabled. Do you think it will work?, do you know a better solution?.
Thanks in advance for your time!!
You need CSS to create APDiv layers too. So there's nothing to be gained here.
Isn´t there anything to put over the honeypot field to hide it from users without using CSS or anything else that could be disabled?.
In a word, no.
Don't lose sleep over this. I've been using hidden fields on forms for years and it's never been a problem.
If you don't like the hidden field approach, add a simple question to your forms that spam bots can't answer.
"Which day of the week follows Tuesday?"
"How many are in a dozen?"
Ok and thanks very much!, I buy honeypot, it seems almost perfect!. Another issue I have just read about it: the honeypot field may be filled as well by the web browser's autocomplete function for users so we would treat them as bots. To avoid it we could add autocomplete="off", it seems it works for most browsers.
Do you know if it really works fine?.
Again, I don't see this as an issue to worry about. I put my hidden field at the very top of the form. Browser autocomplete only activates when the form input field is a) in focus by mouse click or tab key and b) when user types a character into the field. Since humans can't see the field, it never reaches focus.
Europe, Middle East and Africa