-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Test :user-invalid after input and focus change #9346
Comments
Would it be possible to try writing a test with regular keypress events (and maybe .focus() to shift the focus)? I'd expect that will pass: although an UA could in theory decide not to allow scripts to trigger If you make it a self-describing reftest, then the description can detail the requisite manual steps and note that a UA is still considered passing if it fails as scripted reftest but passes the manual-interactive version--that way anyone investigating a fail condition will be alerted to that point, and we have a test without being blocked on #7434. |
@foolip Sounds good! |
@kereliuk, do you think that |
@foolip I think it should probably work now! Here is an example of a test: https://github.com/w3c/web-platform-tests/blob/master/html/editing/focus/sequential-focus-navigation-and-the-tabindex-attribute/focus-tabindex-negative.html |
@kereliuk, cool, I've assigned this to myself to give it a try! |
@gsnedders, before I try this, does testdriver.js work with reftests? |
@foolip I think we decided to punt on that until we actually had a need for it? |
@gsnedders oh, so deliberately punted, I didn't remember that. Well, here I do need it :) webcompat/web-bugs#17453 (comment) is going to be another case requiring it. Can you file an issue detailing what would need to change? |
#13183 filed for that. |
#8899 introduced a basic test for
:user-error
, but in w3c/csswg-drafts#1329 (comment) @fantasai also agreed that testing against this condition would be in line with the spec:typing at least one character and then moving the focus to another input element
This is blocked on #7434. @kereliuk, could you poke me when it's possible to write such a test, so that I can give it a try?
The text was updated successfully, but these errors were encountered: