Improve role date selection #1658
Conversation
fofr
commented
Aug 13, 2014
|
* Starting from 1700 and having to scroll all the way down to 2014, or even 2019, is painful * Restrict date entries to current year rather than current year + 5 which seemed to be the default
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hurray!
… Lisa Scott
Associate Product Manager, GOV.UK
Government Digital Service, Aviation House, 125 Kingsway, London WC2B 6NH
***@***.***
Product updates for GOV.UK: https://insidegovuk.blog.gov.uk/
GDS blog: http://digital.cabinetoffice.gov.uk/
Please use the support form! https://www.gov.uk/support/internal
On 13 Aug 2014, at 10:25, Paul Hayes ***@***.*** wrote:
Before:
After:
—
Reply to this email directly or view it on GitHub.
|
Looks good to me.
On 13 Aug 2014, at 13:37, Paul Hayes notifications@github.com wrote:
|
@@ -9,15 +9,15 @@ | |||
disabled: !form.object.new_record? %> | |||
|
|||
<% if form.object.new_record? %> | |||
<p>Once an appointment has been created the person cannot be changed, to preserve this person's relationship to any associated speeches.</p> | |||
<p>Once an appointment has been created the person cannot be changed, this is to preserve the person’s relationship to associated speeches.</p> |
dhwthompson
Aug 13, 2014
Contributor
I’m not sure this sentence still holds together with just a comma. I’m no content designer, but could I suggest using a semicolon instead?
I’m not sure this sentence still holds together with just a comma. I’m no content designer, but could I suggest using a semicolon instead?
alext
Aug 13, 2014
Contributor
Or even just 2 sentences?
Or even just 2 sentences?
tekin
Aug 13, 2014
Contributor
Agreed. Full stop instead of comma.
Agreed. Full stop instead of comma.
fofr
Aug 13, 2014
Author
Contributor
I agree. Two sentences. Rebased.
I agree. Two sentences. Rebased.
* The second part of the sentence was hard to understand
Code looks good |