This question is locked. New answers and comments are not allowed.
Hello,
We are working with the latest Q2 2011 Beta MVC Extensions and we may have identified a bug. We have a DropDownList control being utilized and based on a specific condition we disable/enable the control as follows:
In some scenarios, the $('#FooID') control may already be enabled. In Q1 2011 it handled the case where the control is already enabled and we try to enable it again. Now, in the Q2 2011 Beta this scenario blocks the drop down from actually dropping down. You can down arrow through the data items (with the keyboard) but you do not get the animation of the drop down. If we comment out the .enable(); line all is well for that scenario but in the scenario where we DO want to enable it no longer works (For obvious reasons).
Is this a known issue? If so is there a hotfix?
We are working with the latest Q2 2011 Beta MVC Extensions and we may have identified a bug. We have a DropDownList control being utilized and based on a specific condition we disable/enable the control as follows:
if (dataItem.FooID > 0){ $('#FooID').data("tDropDownList").disable(); } else { $('#FooID').data("tDropDownList").enable(); }In some scenarios, the $('#FooID') control may already be enabled. In Q1 2011 it handled the case where the control is already enabled and we try to enable it again. Now, in the Q2 2011 Beta this scenario blocks the drop down from actually dropping down. You can down arrow through the data items (with the keyboard) but you do not get the animation of the drop down. If we comment out the .enable(); line all is well for that scenario but in the scenario where we DO want to enable it no longer works (For obvious reasons).
Is this a known issue? If so is there a hotfix?