darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-06-06 22:40:57 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
17f74cf621ced95f044b4ee467441928b5b80e50
notifications-admin/app/templates/views/support/form.html

41 lines
1.5 KiB
HTML
Raw Normal View History

Feedback page working with all tests passing. Updated to include team id. Give Feedback -> Give feedback
2016-04-19 13:51:16 +01:00
{% extends "withoutnav_template.html" %}
{% from "components/textbox.html" import textbox %}
Add standard back links to the support journey Removes the non-standard, bottom of page back links where present. Adds sticky footer to pages with long text boxes.
2019-10-17 13:27:52 +01:00
{% from "components/page-footer.html" import sticky_page_footer %}
{% from "components/page-header.html" import page_header %}
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 %}
Feedback page working with all tests passing. Updated to include team id. Give Feedback -> Give feedback
2016-04-19 13:51:16 +01: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 %}
Use the same template for problems and questions
2020-03-24 15:22:00 +00:00
{{ page_title }}
Feedback page working with all tests passing. Updated to include team id. Give Feedback -> Give feedback
2016-04-19 13:51:16 +01:00
{% endblock %}
{% block maincolumn_content %}
Add standard back links to the support journey Removes the non-standard, bottom of page back links where present. Adds sticky footer to pages with long text boxes.
2019-10-17 13:27:52 +01:00
{{ page_header(
Use the same template for problems and questions
2020-03-24 15:22:00 +00:00
page_title,
Go back to triage page if you’ve come from there
2020-03-25 12:17:39 +00:00
back_link=back_link
Add standard back links to the support journey Removes the non-standard, bottom of page back links where present. Adds sticky footer to pages with long text boxes.
2019-10-17 13:27:52 +01:00
) }}
Replace `grid-row` with `govuk-grid-row` Replaced all instances of `grid-row` in the HTML and JavaScript with `govuk-grid-row`, which is the new GOV.UK Frontend class.
2020-02-19 11:57:15 +00:00
<div class="govuk-grid-row">
Replace `column-two-thirds` with `govuk-grid-column-two-thirds`
2020-02-19 12:36:02 +00:00
<div class="govuk-grid-column-two-thirds">
Add a ‘general’ ticket type This is for tickets coming from non-logged-in users. It’s effectively the same as reporting a problem, but doesn’t have the banner about the status page (because we can’t tell if they’re actually reporting a problem now we’re not asking). It also gives a more generic page title.
2020-03-24 15:45:13 +00:00
{% if show_status_page_banner %}
Use the same template for problems and questions
2020-03-24 15:22:00 +00:00
<div class="panel panel-border-wide">
Don’t allow paragraphs without class attribute All paragraphs should have class="govuk-body", or be otherwise custom-styled. This commit adds some extra checks to our test fixture that looks for paragraphs that don’t have any styling. Our test coverage is pretty good, so this should check almost all pages, and prevent regressions. I’ve done this in such a way that it can be extended for other elements (e.g. links) in the future.
2020-05-29 17:11:01 +01:00
<p class="govuk-body">
Use the same template for problems and questions
2020-03-24 15:22:00 +00:00
Check our <a class="govuk-link govuk-link--no-visited-state" href="https://status.notifications.service.gov.uk">system status</a>
page to see if there are any known issues with GOV.UK Notify.
</p>
</div>
{% endif %}
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() %}
Enable autosizing for some textboxes This commit makes textboxes auto-resize any time they might be used to enter long passages of text which would otherwise make them scroll internally.
2019-10-16 16:34:18 +01:00
{{ textbox(form.feedback, width='1-1', hint='', rows=10, autosize=True) }}
Don’t ask for a user’s email address if we know it If a user is logged in then we already know their name and email address. So there’s no need for them to fill them again on the support form. One concern we might have about this is the user not realising we’re doing this, and the feedback form looking like a bit of a black hole. So we’re replaying their email address on this page to reassure them that: - we know who they are - and that they’ll get a reply
2016-12-12 11:31:26 +00:00
{% if not current_user.is_authenticated %}
Convert EmailFields to GovukEmailFields Changes those fields (and sometimes also regular text input fields) in the following forms: - LoginForm - RegisterUserForm - ChangeEmailForm - FeedbackOrProblem - AcceptAgreementForm - ChangeNameForm (only name field here, but used in the same template field as ChangeEmailForm here: app/templates/views/user-profile/change.html) Also includes changes to templates that use this form and associated tests.
2020-08-07 15:16:04 +01:00
{{ form.name(param_extensions={"classes": "govuk-!-width-full"}) }}
{{ form.email_address(param_extensions={"classes": "govuk-!-width-full"}) }}
Don’t ask for a user’s email address if we know it If a user is logged in then we already know their name and email address. So there’s no need for them to fill them again on the support form. One concern we might have about this is the user not realising we’re doing this, and the feedback form looking like a bit of a black hole. So we’re replaying their email address on this page to reassure them that: - we know who they are - and that they’ll get a reply
2016-12-12 11:31:26 +00:00
{% else %}
Don’t allow paragraphs without class attribute All paragraphs should have class="govuk-body", or be otherwise custom-styled. This commit adds some extra checks to our test fixture that looks for paragraphs that don’t have any styling. Our test coverage is pretty good, so this should check almost all pages, and prevent regressions. I’ve done this in such a way that it can be extended for other elements (e.g. links) in the future.
2020-05-29 17:11:01 +01:00
<p class="govuk-body">We’ll reply to {{ current_user.email_address }}</p>
Don’t ask for a user’s email address if we know it If a user is logged in then we already know their name and email address. So there’s no need for them to fill them again on the support form. One concern we might have about this is the user not realising we’re doing this, and the feedback form looking like a bit of a black hole. So we’re replaying their email address on this page to reassure them that: - we know who they are - and that they’ll get a reply
2016-12-12 11:31:26 +00:00
{% endif %}
Add standard back links to the support journey Removes the non-standard, bottom of page back links where present. Adds sticky footer to pages with long text boxes.
2019-10-17 13:27:52 +01:00
{{ sticky_page_footer('Send') }}
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 %}
Feedback page working with all tests passing. Updated to include team id. Give Feedback -> Give feedback
2016-04-19 13:51:16 +01:00
</div>
</div>
Added route to the system status page to the feedback page
2016-11-21 11:25:57 +00:00
{% endblock %}
Reference in New Issue Copy Permalink