-
Notifications
You must be signed in to change notification settings - Fork 226
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
Add Dragon bug to date input guidance #782
Labels
Comments
9 tasks
I think once we've tackled alphagov/govuk-frontend#1449 we can close this without updating the guidance as the Dragon bug will no longer affect the date input component. |
36degrees
moved this from Upcoming sprints
to Sprint Backlog
in Design System Sprint Board
Jan 15, 2020
Closed
8 tasks
As documented in alphagov/govuk-frontend#1101 this has now been fixed, so we do not need to document it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
alphagov/govuk-frontend#1101 is not a problem with our implementation but with Dragon and it's been reported to them. We should try to reproduce this to confirm the Dragon versions and browsers affected and then document the problem. I spoke to Amy and we agreed that it would be good to put this under "Known issues and gaps" in the date input guidance, similar to what we do with the character count.
The text was updated successfully, but these errors were encountered: