1. 14 Sep, 2018 1 commit
  2. 07 Sep, 2018 1 commit
  3. 06 Sep, 2018 1 commit
  4. 07 Aug, 2018 1 commit
  5. 30 Jul, 2018 3 commits
  6. 24 Jul, 2018 1 commit
  7. 01 Jun, 2018 1 commit
  8. 11 Apr, 2018 1 commit
  9. 23 Feb, 2018 1 commit
  10. 13 Feb, 2018 1 commit
  11. 25 Jan, 2018 1 commit
  12. 22 Dec, 2017 1 commit
  13. 21 Dec, 2017 1 commit
  14. 06 Sep, 2017 1 commit
  15. 02 Sep, 2017 1 commit
  16. 18 Aug, 2017 1 commit
  17. 12 Jul, 2017 1 commit
  18. 06 Jul, 2017 1 commit
  19. 24 Jun, 2017 1 commit
  20. 23 Jun, 2017 1 commit
  21. 22 Jun, 2017 1 commit
  22. 13 Jun, 2017 1 commit
  23. 07 Jun, 2017 1 commit
  24. 05 May, 2017 1 commit
  25. 03 May, 2017 1 commit
  26. 20 Apr, 2017 1 commit
  27. 13 Apr, 2017 2 commits
  28. 21 Mar, 2017 1 commit
  29. 24 Jan, 2017 1 commit
  30. 03 Jan, 2017 1 commit
  31. 31 Dec, 2016 2 commits
  32. 27 Sep, 2016 1 commit
  33. 30 Jun, 2016 1 commit
  34. 29 Jun, 2016 1 commit
  35. 04 May, 2016 1 commit
  36. 05 Apr, 2016 1 commit
    • Robert Speicher's avatar
      Standardize the way we check for and display form errors · 7a2370f7
      Robert Speicher authored
      - Some views had a "Close" button. We've removed this, because we don't
        want users accidentally hiding the validation errors and not knowing
        what needs to be fixed.
      - Some views used `li`, some used `p`, some used `span`. We've
        standardized on `li`.
      - Some views only showed the first error. We've standardized on showing
        all of them.
      - Some views added an `#error_explanation` div, which we've made
        standard.
      7a2370f7