? ? ? Pending

User tests: Successful: Unsuccessful:

avatar coolcat-creations
coolcat-creations
4 Jan 2018

Summary of Changes

Altough Honeypot is not really a "captcha" functionality I think it fits best in the captcha plugin group. This plugin creates a hidden field named "repeatmail". The field name can be changed by the user. If repeatmail is filled, the form can't be sent.

Testing Instructions

Enable the Honeypot in the Captcha Options in your main configuration.

  • Use the Contactform and send a mail -> everything should work as before
  • Use element inspector to disable the StyleDeclaration that hides the field and fill the field, try to send the form, an error should appear.

Documentation Changes Required

Yes, as it's a new feature

avatar coolcat-creations coolcat-creations - open - 4 Jan 2018
avatar coolcat-creations coolcat-creations - change - 4 Jan 2018
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 4 Jan 2018
Category Administration Language & Strings Front End Plugins
avatar coolcat-creations coolcat-creations - change - 4 Jan 2018
Labels Added: ? ?
avatar coolcat-creations coolcat-creations - edited - 4 Jan 2018
avatar coolcat-creations coolcat-creations - change - 4 Jan 2018
The description was changed
avatar brianteeman
brianteeman - comment - 4 Jan 2018

Personally I dont see the need to add this to the core

avatar coolcat-creations
coolcat-creations - comment - 4 Jan 2018

Google Captcha v1 and v2 are outdated and the new "invisible recaptcha" creates a always visible google flag. I think a honeypot solution is much more userfriendly and does not display large flags like this in the page corner:
grafik

avatar coolcat-creations coolcat-creations - change - 4 Jan 2018
Labels Added: ?
avatar brianteeman
brianteeman - comment - 4 Jan 2018

Why do you allow the field name to be changed? Remember that as the field is only hidden from sighted users so in order for this to work as intended the fieldname must be something that a user of assistive technology would not think they need to complete,

avatar coolcat-creations
coolcat-creations - comment - 6 Jan 2018

@C-Lodder the body scope was on purpose to enforce hiding the label without using an important. I mean when any 3rd Party Template would have a style for that. What do you think, should I really remove the scope?

avatar coolcat-creations
coolcat-creations - comment - 6 Jan 2018

@brianteeman thought i would keep it flexible when allowing to change the fieldname so if someone woukd have a repeatmail field for real the conflict could be resolved. How to tell screenreaders that this field is not important i will investigate.

avatar brianteeman
brianteeman - comment - 6 Jan 2018

. How to tell screenreaders that this field is not important i will investigate.

As far as I am aware that is not possible

avatar coolcat-creations
coolcat-creations - comment - 11 Jan 2018

I got some more feedback outside this PR and want to put it on hold for a few weeks until I have the time to implement all suggestions. Thanks for reviewing to everyone.

avatar coolcat-creations
coolcat-creations - comment - 5 Apr 2018

I searched for different possibilities to make the Honeypot - really - accessible but i did not found a method. I think we need something in core that is Google-Independant - but i have no idea what. Closing this for now.

avatar coolcat-creations coolcat-creations - change - 5 Apr 2018
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2018-04-05 12:31:56
Closed_By coolcat-creations
avatar coolcat-creations coolcat-creations - close - 5 Apr 2018

Add a Comment

Login with GitHub to post a comment