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
I have a question about the implementation of the HtmlControlFor and more specifically the methods SelectElementByText and SelectElement. Why the first one does use .change() of jQuery and the second one doesn't. Basically this forces me to create my custom function to select an option from a dropdown as we use Knockout and if we just change the value without calling .change() then the observable is not updated.
Is this done for some legit reason or is it a bug?
The text was updated successfully, but these errors were encountered:
I have a question about the implementation of the HtmlControlFor and more specifically the methods SelectElementByText and SelectElement. Why the first one does use .change() of jQuery and the second one doesn't. Basically this forces me to create my custom function to select an option from a dropdown as we use Knockout and if we just change the value without calling .change() then the observable is not updated.
Is this done for some legit reason or is it a bug?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
I have a question about the implementation of the HtmlControlFor and more specifically the methods SelectElementByText and SelectElement. Why the first one does use .change() of jQuery and the second one doesn't. Basically this forces me to create my custom function to select an option from a dropdown as we use Knockout and if we just change the value without calling .change() then the observable is not updated.
Is this done for some legit reason or is it a bug?
The text was updated successfully, but these errors were encountered: