Describe the bug
When a soho-lookup is initially disabled, for instance with the [isDisabled]="true" input, or when calling setDisabledState(true) when the host component is initiated, the component cannot be enabled again. The input field looks enabled, but it keeps the is-disabled class and the button has the disabled attribute forever.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The lookup button and field should no longer be disabled.
Version
Platform
Additional context
Issue observed in Homepages widget.
NOTE: If possible, we would like a patch for [email protected] and/or [email protected] since Angular 12 is stopping us from upgrading to the latest version
@ericangeles can you or someone in manilla please prioritize this fix to main branch. After will have to patch 4.51
I can take a look if it's urgent @tmcconechy
Yes it is thanks @ericangeles
Thanks @bthharper @tmcconechy & team!
The fix #1076 appears to have solved our issue.
I created a manual patch for our project (on 9.5.0) with the changes so I don't think we need an upstream patch.
Awesome, thanks for the update. I had forgotten about the patch. So glad its resolved
Most helpful comment
Thanks @bthharper @tmcconechy & team!
The fix #1076 appears to have solved our issue.
I created a manual patch for our project (on 9.5.0) with the changes so I don't think we need an upstream patch.