Skip to content
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

Add test for auto-complete #2

Closed
aik099 opened this issue Sep 28, 2016 · 3 comments
Closed

Add test for auto-complete #2

aik099 opened this issue Sep 28, 2016 · 3 comments

Comments

@aik099
Copy link
Member

aik099 commented Sep 28, 2016

The test needs to be added, that confirms, that auto-complete controls (e.g. jQueryUI.AutoComplete) for JS-enabled drivers works as expected:

  • you can type a test
  • a dropdown appears with a suggestions
  • clicking on a suggestion puts it into the input
  • [not sure about this one] the change event is fired

Right now due way how it's implemented at least for MinkSelenium2Driver this is a big issue.

@aik099
Copy link
Member Author

aik099 commented Sep 28, 2016

With minkphp/MinkSelenium2Driver#244 merged it might actually allow test added in here to pass, because then focus won't be moved away from the field (we're pressing TAB right now) and auto-complete control won't be closed.

@uuf6429
Copy link
Member

uuf6429 commented Jul 9, 2023

@aik099 a bit of an old issue, but in principle I don't think this is doable.
There is no standard way how these custom controls would behave. Having such a test for a custom control will likely only work for that very specific implementation, and nothing else.

What probably makes more sense is to have a jQuery UI test suite developed and maintained by the jQuery folks, which would improve quality on both sides...

@aik099
Copy link
Member Author

aik099 commented Jul 22, 2023

There is no standard way how these custom controls would behave. Having such a test for a custom control will likely only work for that very specific implementation, and nothing else.

With the above-mentioned issue already merged and a slow auto-complete related issue rate (3 or fewer people since issue creation time had this problem) I think, that this issue can be safely closed.

What probably makes more sense is to have a jQuery UI test suite developed and maintained by the jQuery folks, which would improve quality on both sides...

Maybe.

@aik099 aik099 closed this as completed Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants