Skip to content

Conversation

@thewilkybarkid
Copy link

Most examples of honeypots (including the default field name here) are for email address fields, so might be better to use an actual email type.

@isometriks
Copy link
Owner

Hmm. I'm torn between the fact that if anything is put into the field that it should fail, and that if it's an email field maybe a bot would be more inclined to fill it in knowing it's an email field.

@ThomasLandauer
Copy link
Contributor

@isometriks Don't understand what you mean :-(

If the form already has an email address which is rendered as EmailType, it's odd (i..e obvious for the bot) if the "second" email field is a TextType.
On the other hand, if you call the honeypot field last_name, it shouldn't be rendered as EmailType...

So to me there's only one solution to this: Another option! I would call it type - same as Symfony https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/FormBuilderInterface.php#L30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants