Fixed an issue with Klaro autofocus #510
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Klaro loses its autofocus when the main page, into which Klaro has been loaded, focuses on one of its own elements. Accepting or rejecting cookie consent should be first thing on focus (if the
autofocus
is set totrue
in config). This is an accessibility issue for keyboard navigation.To test this issue in action:
autofocus
totrue
in config.js located inklaro-js/dist/config.js
simple.html
located inklaro-js/dist/examples/simple.html
, add an input element in the body with an id, for example<input id="autofocus-test"></input>
, then create a new script tag like so<script>document.getElementById("autofocus-test").focus()</script>
simple.html
will result the focus going to the input box instead of klaro's cookie notice.