-
Notifications
You must be signed in to change notification settings - Fork 99
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
No interaction possible with "invisible" input fields #569
Comments
Annoying these JavaScript frameworks. I don't believe there currently is a 'standard' way to deal with this. A subclass of BrowserTest could probably hide the magic to shift focus, so the test scripts are not polluted with it. Similar tricks were needed for Angular 1 and RichFaces validations. Having said that I expect fixing the 'click' behaviour might be possible in the generic browser test. I believe the labels are not hidden/opaque until focused so that could be an extra trick to learn browser test (I'm actually surprised it doesn't at the moment), but I haven't really looked into it. |
I managed to make click and enter work using a custom subclass.
With a setup like this you can isolate the changes to code so the actual test/wiki pages only have to use another fixture, but their steps are the same.
Maybe you can use this as a starting point and see what is needed to make a fixture that is fully functional with Vue, for your suite? I would be happy to add it if you submit a PR with it. |
After updating our UI from vuetify 2 to vuetify 3 no interactions is possible with input fields.
The significant change I see is the way how input field is now embedded in the vutify TextField component. In the new version the input field has the 'opactiy: 0' set which will change to 1 if the element is focused/active.
It seems that 'enter' just 'doesn't see' the corresponding input field. Also 'click' ignores it.
The current workaround is to use JS to focus the element to go on with the test, but is there an 'official' way to avoid it?
Here are the tests to show the problem.
vutify 2 (working)
vuetify 3 (not working)
vuetify 3 (working with workaround)
The text was updated successfully, but these errors were encountered: