app/templates/partials/count.html

{% from "components/big-number.html" import big_number %}
{% from "components/pill.html" import pill %}

<div class="ajax-block-container">
  {% if notifications_deleted %}
    <div class="govuk-grid-row bottom-gutter-1-2">
      {% for label, query_param, url, count in counts %}
        <div class="govuk-grid-column-one-quarter">
          {{ big_number(count, label, smaller=True) }}
        </div>
      {% endfor %}
    </div>
  {% else %}
    <div class="bottom-gutter">
      {{ pill(counts, request.args.get('status', '')) }}
    </div>
  {% endif %}
</div>
Don’t show blue boxes once notifications have gone You can click the blue boxes to filter the list of notifications. Once the notifications have gone there’s nothing to filter, so we should just show the numbers but without them being clickable. 2019-12-30 16:53:45 +00:00			`{% from "components/big-number.html" import big_number %}`
Make jobs filterable by notification status We can filter all notifications by status already. This commit reuses the same code to filter the notifications for a job by status. This means that, visually we can show the count on a job the same as we do for all notifications, which is similar to how we show the counts on the dashboard, so hopefully it feels like a bit more of a solid thing. This also applies to CSV downloads and AJAX updates, which will inherit any filtering that their parent page has applied. 2016-06-08 16:34:26 +01:00			`{% from "components/pill.html" import pill %}`
Patch update sections of the page on AJAX Currently, when we update a section of the page with AJAX we replace the entire HTML of the section with the new HTML. This causes problems: - if you’re trying to interact with that section of the page, eg by inpecting it, clicking or hovering an element - (probably) for screenreaders trying to navigate a page which is changing more than is necessary This commit replaces the call to `.html()` with a pretty clever library called diffDOM[1]. DiffDOM works by taking a diff of the old element and the new element, then doing a patch update, ie only modifying the parts that have changed. This is similar in concept to React’s virtual DOM, while still allowing us to render all markup from one set of templates on the server-side. 1. https://github.com/fiduswriter/diffDOM 2016-04-27 09:28:42 +01:00
Don’t show blue boxes once notifications have gone You can click the blue boxes to filter the list of notifications. Once the notifications have gone there’s nothing to filter, so we should just show the numbers but without them being clickable. 2019-12-30 16:53:45 +00:00			`<div class="ajax-block-container">`
			`{% if notifications_deleted %}`
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 bottom-gutter-1-2">`
Don’t show blue boxes once notifications have gone You can click the blue boxes to filter the list of notifications. Once the notifications have gone there’s nothing to filter, so we should just show the numbers but without them being clickable. 2019-12-30 16:53:45 +00:00			`{% for label, query_param, url, count in counts %}`
Replace `column-one-quarter` with `govuk-grid-column-one-quarter` 2020-02-19 12:53:59 +00:00			`<div class="govuk-grid-column-one-quarter">`
Don’t show blue boxes once notifications have gone You can click the blue boxes to filter the list of notifications. Once the notifications have gone there’s nothing to filter, so we should just show the numbers but without them being clickable. 2019-12-30 16:53:45 +00:00			`{{ big_number(count, label, smaller=True) }}`
			`</div>`
			`{% endfor %}`
			`</div>`
			`{% else %}`
			`<div class="bottom-gutter">`
			`{{ pill(counts, request.args.get('status', '')) }}`
			`</div>`
			`{% endif %}`
Patch update sections of the page on AJAX Currently, when we update a section of the page with AJAX we replace the entire HTML of the section with the new HTML. This causes problems: - if you’re trying to interact with that section of the page, eg by inpecting it, clicking or hovering an element - (probably) for screenreaders trying to navigate a page which is changing more than is necessary This commit replaces the call to `.html()` with a pretty clever library called diffDOM[1]. DiffDOM works by taking a diff of the old element and the new element, then doing a patch update, ie only modifying the parts that have changed. This is similar in concept to React’s virtual DOM, while still allowing us to render all markup from one set of templates on the server-side. 1. https://github.com/fiduswriter/diffDOM 2016-04-27 09:28:42 +01:00			`</div>`