You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a browser without HTML5 date field support (e.g. Safari) if you enter the dates in events or news CWP pages using the format in the field labels and search, it comes back as a different format to that suggested:
You don't notice this with a date picker field because it presents it as a browser rendered UI control instead.
The text was updated successfully, but these errors were encountered:
Taking the NZ govt style guide as a reference (it doesn't explicitly call this out) we should look at changing the expect format in the backend and field label to be dd mm yyyy, not yyyy mm dd as part of this too.
@sachajudd - #59 changed the format of the labels to match the example input format when you're using a browser that supports date picker fields.
This issue still remains in that if your browser doesn't support native HTML5 datepickers, the field label example is still not the same as the input field. The label would say (example 12/05/1995) but the field's format would be 1995-05-12.
My suggestion would be to drop the example from the label entirely.
CWP 2.3.x-dev
In a browser without HTML5 date field support (e.g. Safari) if you enter the dates in events or news CWP pages using the format in the field labels and search, it comes back as a different format to that suggested:
You don't notice this with a date picker field because it presents it as a browser rendered UI control instead.
The text was updated successfully, but these errors were encountered: