Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade GOV.UK Template, Frontend Tookit, and Elements #1222

Merged
merged 8 commits into from
Apr 11, 2017
Merged

Conversation

quis
Copy link
Member

@quis quis commented Apr 10, 2017

We should make sure that the parts of the UI that we inherit from these packages are kept up to date.

This commit:

  • updates each dependency to the latest version
  • makes patch (bug fixing) version bumps automatic because
    • it makes less work for us
    • we don’t get so far behind
    • we should be able to trust dependencies that are coming from other teams in this building

Full changes that this brings in:

GOV.UK Template

GOV.UK Elements

GOV.UK Frontend Toolkit

Major visual changes

Darker borders around text input elements

image

New radio and checkbox inputs

screen shot 2017-04-10 at 14 54 28

screen shot 2017-04-10 at 14 54 48

image

quis added 8 commits April 10, 2017 14:02
We should make sure that the parts of the UI that we inherit from these
packages are kept up to date.

This commit:
- updates each dependency to the latest version
- makes patch (bug fixing) version bumps automatic because
  - it makes less work for us
  - we don’t get so far behind
  - we should be able to trust dependencies that are coming from other
    teams in this building

Full changes that this brings in:

GOV.UK Template
---

- Increase skiplink colour contrast ([GOV.UK Template PR #263](alphagov/govuk_template#263))

GOV.UK Elements
---
- Too many to show – see
  alphagov/govuk_elements@v1.1.1...v3.0.2#diff-4ac32a78649ca5bdd8e0ba38b7006a1e

GOV.UK Frontend Toolkit
---
- Too many to show – see
  alphagov/govuk_frontend_toolkit@v4.6.0...v5.2.0#diff-4ac32a78649ca5bdd8e0ba38b7006a1e
Previously the beta bar was orange, which we didn’t want. So we wrote
some SASS to make it blue.

Now that GOV.UK Frontend Toolkit makes it blue, we can remove this SASS.

See alphagov/govuk_frontend_toolkit#370
The external link icon, and associated mixin, were deprecated in
alphagov/govuk_frontend_toolkit#293

This means we can’t and shouldn’t use them any more.
The visual appearance of radio and checkbox form inputs changed in
GOV.UK Elements here:

alphagov/govuk_elements#296

This was subsequently reimplemented with different markup and no
Javascript here:
alphagov/govuk_elements#406

This has meant making the following changes to our app:
- changing the markup in our radio/checkbox macros to match the example
  markup given by GOV.UK Elements
- removing the previous Javascript file because it’s no longer needed to
  make the radios appear visual selected
- making the buttons on the scheduled job picker look like links,
  because the grey button style looked weird with the new radio buttons
The Elements CSS was making the `label` and `input` of disabled radio
buttons `opacity: 0.5`. This was resulting in text that was:
- too pale, especially where we were nesting 16px ‘hint’ text inside the
  label
- waaaay too pale when inside a link inside the label

This commit overrides elements to dim the disabled radio button by
making it’s text colour grey, rather than making the whole thing
semi-transparent.
Not sure why we were doing this. But as part of the Elements upgrade
our back buttons got bigger (because they weren’t constrained by the
line in our `app.scss`) but any green submit buttons stayed smaller in
height, so didn’t line up.

This commit removes the override, so all buttons have the size that
Elements intended.
GOV.UK Elements changed tables to be a larger font size here:
alphagov/govuk_elements#185

This is good in principle (and a lot of our tables are 19px already).
However, the ones that aren’t are still 16px because there’s a lot of
info to fit on the page (eg when previewing someone’s CSV file).
Copy link
Contributor

@leohemsted leohemsted left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

think this all looks good but all those jinja templates give my brain a parsing error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants