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
{{ message }}
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
Jesse, are you sure we need all of this? Calling DOM focus() method will in fact apply CSS properly, and the CSS can be retreived e.g. with getComputedStyle. You might check it at focus() + getComputedStyle() demo.
Adding an extra states like peding, will add more complexity to this solution, while we can stick to vanilla JS.
So, this is really silly. Thanks for calling this out. What I was doing, was calling $0.focus() on elements from the Inspector...BUT...if the inspector has focus, then nothing in the page has focus. So calling focus from the inspector, although it sets document.activeElement doesn't appear to change the styling.
I set up a call to focus in setTimeout then moved focus to the page. Sure enough, the styling is triggered on Focus.
Derp derp derp.
jessebeach
changed the title
Cases need to expose a pending state that allows a web driver to take an action
Reenable the focusIndicatorVisible test in the master branch.
Aug 13, 2015
Cool! And you're right, browsers do drop focus presentation the moment you minimize the browser. That makes integration tests for JS so much more painful. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reenable the
focusIndicatorVisible
test in the master branch.https://github.com/quailjs/quail/blob/master/lib/assessments/focusIndicatorVisible.js
!! Important !!
You'll need to go into
tests.yml
and uncomment thefocusIndicatorVisible
test, then rebuild quail in order for this assessment to be available. Run:in the CLI, and you're off to the races.
The text was updated successfully, but these errors were encountered: