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 was archived by the owner on Apr 12, 2024. It is now read-only.
Would it be possible for someone to work on the code used to test the <SELECT>. It seems there are a large number of issues with this form control and every time one bug is fixed another one or two come up. I'm really wondering if there will ever be a day when there are no select control related issues.
The text was updated successfully, but these errors were encountered:
Do you have any specific suggestions? Obviously it would be better to have all possible cases tested, but this is difficult because select is so complex and can be used in a variety of ways. I believe most of the recent select issues have been causes by a huge refactoring shortly before the 1.3 release. When these issues are fixed, we include tests for broken cases.
@rscholey what would really hope is to have a minimal, live reproduce scenario using plunker or similar for the cases you are facing. For example there is #9918 reported but no clear reproduce scenario. We can quickly turn reproduce scenarios into test + fix, provided that we can see the issue.
@rscholey I was able to reproduce #9714 and just submitted a pull request with a fix. It contains a unit test for using $timeout with select, which will hopefully help to prevent future issues of this kind.
Would it be possible for someone to work on the code used to test the
<SELECT>
. It seems there are a large number of issues with this form control and every time one bug is fixed another one or two come up. I'm really wondering if there will ever be a day when there are no select control related issues.The text was updated successfully, but these errors were encountered: