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

The functionality of what-input.min.js #7983

Closed
dily86 opened this Issue Jan 24, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@dily86

dily86 commented Jan 24, 2016

Hello,

Id like to know the functionality of what-input.min.js include in Zurbs foundation-6 framework , in the js/vendor directory, please.

Thanks for your answers,

@gakimball

This comment has been minimized.

Show comment
Hide comment
@gakimball

gakimball Jan 24, 2016

Collaborator

All of our components add outlines to focus/active states to make them accessible to keyboard users. However, designers find those outlines ugly, but they're necessary for accessibility.

what-input watches for what input device the user is using, mouse or keyboard. If it's a mouse, the outlines are removed in the CSS. If it's a keyboard, the outlines are kept as a navigational aid.

It's technically an optional dependency—you can remove it if you want. However, we highly recommend keeping it.

Collaborator

gakimball commented Jan 24, 2016

All of our components add outlines to focus/active states to make them accessible to keyboard users. However, designers find those outlines ugly, but they're necessary for accessibility.

what-input watches for what input device the user is using, mouse or keyboard. If it's a mouse, the outlines are removed in the CSS. If it's a keyboard, the outlines are kept as a navigational aid.

It's technically an optional dependency—you can remove it if you want. However, we highly recommend keeping it.

@gakimball gakimball closed this Jan 24, 2016

@dily86

This comment has been minimized.

Show comment
Hide comment
@dily86

dily86 Jan 24, 2016

ok, thanks a lot. ;-)

dily86 commented Jan 24, 2016

ok, thanks a lot. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment