mastodon/app/views/auth/confirmations/captcha.html.haml

- content_for :page_title do
  = t('auth.captcha_confirmation.title')

= form_tag auth_captcha_confirmation_url, method: 'POST', class: 'simple_form' do
  = render 'auth/shared/progress', stage: 'confirm'

  = hidden_field_tag :confirmation_token, params[:confirmation_token]

  %p.lead= t('auth.captcha_confirmation.hint_html')

  .field-group
    = render_captcha

  .actions
    %button.button= t('challenge.confirm')
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 13:37:12 -08:00			`- content_for :page_title do`
Add some explanation text on the CAPTCHA confirmation page 2022-01-26 04:24:51 -08:00			`= t('auth.captcha_confirmation.title')`
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 13:37:12 -08:00
			`= form_tag auth_captcha_confirmation_url, method: 'POST', class: 'simple_form' do`
[Glitch] Update style of captcha confirmation page to match sign-up form (#2226) 2023-05-25 10:14:37 -07:00			`= render 'auth/shared/progress', stage: 'confirm'`

Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 13:37:12 -08:00			`= hidden_field_tag :confirmation_token, params[:confirmation_token]`

[Glitch] Update style of captcha confirmation page to match sign-up form (#2226) 2023-05-25 10:14:37 -07:00			`%p.lead= t('auth.captcha_confirmation.hint_html')`
Add some explanation text on the CAPTCHA confirmation page 2022-01-26 04:24:51 -08:00
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 13:37:12 -08:00			`.field-group`
Change CAPTCHA handling to be only on email verification This simplifies the implementation considerably, and while not providing ideal UX, it's the most flexible approach. 2022-01-25 14:56:57 -08:00			`= render_captcha`
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 13:37:12 -08:00
			`.actions`
Fix incorrect translation string in glitch-soc captcha feature 2023-02-19 02:02:27 -08:00			`%button.button= t('challenge.confirm')`