app/templates/views/two-factor.html

{% extends "withoutnav_template.html" %}
{% from "components/textbox.html" import textbox %}
{% from "components/checkbox.html" import checkbox %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/form.html" import form_wrapper %}

{% block per_page_title %}
  Text verification
{% endblock %}

{% block maincolumn_content %}

<div class="grid-row">
  <div class="column-two-thirds">
    <h1 class="heading-large">Check your phone</h1>

    <p>We’ve sent you a text message with a security code.</p>

    {% call form_wrapper(class="extra-tracking") %}
      {{ textbox(
        form.sms_code,
        width='5em',
        autofocus=True
      ) }}
      {{ page_footer(
        "Continue",
        secondary_link=url_for('main.check_and_resend_text_code'),
        secondary_link_text='Not received a text message?'
      ) }}
    {% endcall %}
  </div>
</div>

{% endblock %}
-												Make spacing and position of banners consistent

Banners should always be the first thing on the page.

Because headers already have padding we don’t want to put padding on the
container.

So banners should also have top padding to distance then from the red bar.

They should also sit in the 3/4 column if the page has side navigation. This
commit adds a new template (`withoutnav_template.html`) which extends
`admin_template.html`. All views then extend one or the other, never the
`admin_template.html` directly. This means that `admin_template.html` doesn’t
have to make decisions about where the flash messages are displayed.

											
										
										
											2016-02-01 12:15:38 +00:00
+								{% extends "withoutnav_template.html" %}
-												Add a WTForms-compatible textbox macro

This macro:
- accepts a WTForm form field as a parameter
- renders a form field which follows the GOV.UK Elements patterns, both visually
  and in markup terms

It then changes any page which uses either:
- the old, non-WTForms macro or
- the old, WTFforms `render_field` macro

…to use this new macro and removes both of the old ones.

It also adds the option to display hint text above the textbox.

											
										
										
											2016-01-11 13:15:10 +00:00
+								{% from "components/textbox.html" import textbox %}
-												Remember me functionality added and tested.

Merge extra.

Fixed comment.

											
										
										
											2016-02-23 15:45:19 +00:00
+								{% from "components/checkbox.html" import checkbox %}
-												Rename `submit_form` component to `page_footer`

Submit form was
- a confusing name in itself
- not descriptive, because it also has an optional ‘back’ link

This commit also puts this component in as many pages as possible, stripping
out any hard-coded buttons and links.

It replaces any usage of buttons for ‘back’, because these are links, not
buttons (ie they don’t change any data).

											
										
										
											2016-01-07 20:11:22 +00:00
+								{% from "components/page-footer.html" import page_footer %}
-												Use a macro for form tags

This will stop us repeatedly forgetting to add `novalidate` and
`autocomplete='off'` to our forms (which is how most of them are set
up).

It uses sensible defaults, based on how we most-commonly configure
forms:
- most of our forms are `post`ed (but this can be overridden)
- `autocomplete` should only be enabled where it makes sense, otherwise
  it’s more annoying than useful (but this can be overriden)
- we should never be using HTML5 form validation because our own error
  styles and messages are better

											
										
										
											2018-09-19 12:39:36 +01:00
+								{% from "components/form.html" import form_wrapper %}
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
-												Include service name in page `<title>`

In pages specific to a service (e.g. dashboard and sub pages) the title
needs to distinguish which service it applies to. This is mainly to give
context to screen reader users who could be managing multiple services.

Implementing this uses template inheritance:

`page_title` includes `per_page_title` includes `service_page_title`

‘GOV.UK Notify’ is inserted into every page title.

Pages that set `service_page_title` get the service name inserted too.

											
										
										
											2017-02-13 10:45:15 +00:00
+								{% block per_page_title %}
 								  Text verification
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
+								{% endblock %}
-												Make spacing and position of banners consistent

Banners should always be the first thing on the page.

Because headers already have padding we don’t want to put padding on the
container.

So banners should also have top padding to distance then from the red bar.

They should also sit in the 3/4 column if the page has side navigation. This
commit adds a new template (`withoutnav_template.html`) which extends
`admin_template.html`. All views then extend one or the other, never the
`admin_template.html` directly. This means that `admin_template.html` doesn’t
have to make decisions about where the flash messages are displayed.

											
										
										
											2016-02-01 12:15:38 +00:00
+								{% block maincolumn_content %}
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
 								<div class="grid-row">
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								  <div class="column-two-thirds">
-												Reword 2FA page to match email confirmation

											
										
										
											2016-04-23 16:11:41 +01:00
+								    <h1 class="heading-large">Check your phone</h1>
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
-												Change 'verification code' to 'security code'

Extensive testing on Verify has shown that this is understood better.

											
										
										
											2016-08-22 10:17:03 +01:00
+								    <p>We’ve sent you a text message with a security code.</p>
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
-												Use a macro for form tags

This will stop us repeatedly forgetting to add `novalidate` and
`autocomplete='off'` to our forms (which is how most of them are set
up).

It uses sensible defaults, based on how we most-commonly configure
forms:
- most of our forms are `post`ed (but this can be overridden)
- `autocomplete` should only be enabled where it makes sense, otherwise
  it’s more annoying than useful (but this can be overriden)
- we should never be using HTML5 form validation because our own error
  styles and messages are better

											
										
										
											2018-09-19 12:39:36 +01:00
+								    {% call form_wrapper(class="extra-tracking") %}
-												Make two factor textbox consistent with verify textboxes

- make the field the same width (5em to match length of code)
- move ‘haven’t received…’ link underneath the textbox instead of underneath
  the button

											
										
										
											2016-02-02 16:03:30 +00:00
+								      {{ textbox(
 								        form.sms_code,
 								        width='5em',
-												Reword 2FA page to match email confirmation

											
										
										
											2016-04-23 16:11:41 +01:00
+								        autofocus=True
-												Make two factor textbox consistent with verify textboxes

- make the field the same width (5em to match length of code)
- move ‘haven’t received…’ link underneath the textbox instead of underneath
  the button

											
										
										
											2016-02-02 16:03:30 +00:00
+								      ) }}
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								      {{ page_footer(
-												Reword 2FA page to match email confirmation

											
										
										
											2016-04-23 16:11:41 +01:00
+								        "Continue",
-												Requesting a resend of verify code for a user that has not completed
registration will allow user to check and modify mobile number.

Registered (active) users will only be able to request resend to their
existing registered number.

											
										
										
											2016-06-13 16:06:13 +01:00
+								        secondary_link=url_for('main.check_and_resend_text_code'),
-												Reword 2FA page to match email confirmation

											
										
										
											2016-04-23 16:11:41 +01:00
+								        secondary_link_text='Not received a text message?'
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								      ) }}
-												Use a macro for form tags

This will stop us repeatedly forgetting to add `novalidate` and
`autocomplete='off'` to our forms (which is how most of them are set
up).

It uses sensible defaults, based on how we most-commonly configure
forms:
- most of our forms are `post`ed (but this can be overridden)
- `autocomplete` should only be enabled where it makes sense, otherwise
  it’s more annoying than useful (but this can be overriden)
- we should never be using HTML5 form validation because our own error
  styles and messages are better

											
										
										
											2018-09-19 12:39:36 +01:00
+								    {% endcall %}
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								  </div>
-												Create base forms for registration and sign in

Created routes and forms for registration, sign in, and registration
from an invite.
Also tidied up assets folder, removed copy of fronted toolkit.

											
										
										
											2015-11-25 16:21:28 +00:00
+								</div>
-												Updated html title [ci skip]
											
										
										
											2015-12-01 09:55:37 +00:00
+								{% endblock %}