Describe the bug
When the destroy() method for a dropdown control is executed from another dropdown control, the is-open class is not removed from the executing dropdown and the executing dropdown can no longer be opened.
This functionality is required as the soho-dropdown.component in ids-enterprise-ng will execute the destroy() method when the component is removed from a template. In Landmark, there is functionality to dynamically show or remove controls based on some criteria. In this instance, a dropdown is set to be visible when a certain value is selected from another dropdown; otherwise, a text component is set to be visible.
Would like this change to be in 4.13.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect the dropdown to open
Screenshots

Additional context
example-destroy.zip
Are you working on this @fitzorama , or so you need us to assign it to a developer?
I think your folks are better situated to make the change. I came up with something, but believe it to be more of a work around.
http://localhost:4000/components/dropdown/example-destroy.html
http://master-enterprise.demo.design.infor.com/components/dropdown/example-destroy.html
File not found when accessing the URLs above.
Try:
http://localhost:4000/components/dropdown/test-destroy.html
http://master-enterprise.demo.design.infor.com/components/dropdown/test-destroy.html
My fault, as i asked @davidcarlsonberg to rename these as these are more tests than front facing examples. Also there is a unit test for this.
This issue is now resolved. Moving this ticket to the Done folder.