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.
The existing select(...).option(val) in ngScenario will take any option that contains the given value, ignoring whether or not it's an exact match. This results in the following unexpected behaviour.
This actually selects value=A (twenty one) as it contains one. The expected behaviour would be prioritise exact matches, such as value D (one), before selecting any option that contains the value.
The text was updated successfully, but these errors were encountered:
The existing
select(...).option(val)
in ngScenario will take any option that contains the given value, ignoring whether or not it's an exact match. This results in the following unexpected behaviour.This actually selects value=A (twenty one) as it contains
one
. The expected behaviour would be prioritise exact matches, such as value D (one), before selecting any option that contains the value.The text was updated successfully, but these errors were encountered: