-
Notifications
You must be signed in to change notification settings - Fork 364
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
Date picker spin button example broken in Safari #1151
Comments
Further problems at https://www.w3.org/TR/wai-aria-practices/examples/spinbutton/datepicker-spinbuttons.html and http://w3c.github.io/aria-practices/examples/spinbutton/datepicker-spinbuttons.html:
(tested with Chrome and Firefox, Windows 8) |
JAWS outputs: "To set the value use the Arrow keys or type the value", because normally free text input in spin button fields is possible. But not here. Maybe readonly has to be used? Or should text input be made possible? |
Verified that the issue was not happening in Chrome, Firefox, and Edge, but is also happening in IE11. Working on a fix for this specific issue @JAWS-test can you file separate issues for the other things you're finding? |
@JAWS-test made a fix for the issue with the NaN: #1154 |
Thank you so much for fixing the other problems so quickly! |
Resolves issue #1151. The query selector for the `spinbutton` element was incomplete, which caused it to not query properly in Safari or IE. This fix adds in the missing characters to the query so that it queries properly.
Thanks to @backwardok, this is fixed with commit e451c93! |
The example for the
spinbutton
role works well in Chrome, but has a javascript error in Safari.On load, there's a SyntaxError:
The string did not match the expected pattern.
on this line in spinbutton-date.js:domNode.querySelector('[role="spinbutton');
My guess is that Chrome is being generous with the selector here and Safari is breaking because it's technically an invalid selector. It should be
domNode.querySelector('[role="spinbutton]');
(it was missing the closing right bracket)The text was updated successfully, but these errors were encountered: