Steps to reproduce:
<form> wrapper to any ClayDropDown testing environment you have.or, to get the case from attached gif:
CardWithHorizontal, which contains ClayDropDown.<clay:horizontal-card-v2> to <clay:horizontal-card>.What is the expected result?
What actually happens:
Notes:
event.preventDefault(), that handled this case. In Clay 3 component, there is no such thing. On click we are just invoking callback.event.preventDefault()event object to onActiveChange callback, so that form interaction can be controlled from top componentbutton for triggerEnvironment
| Tech | Version |
| ----- | ------- |
| @clayui/drop-down | v3.8.0 |
| @clayui/card | v3.5.0 |
| React | |

/cc @julien @carloslancha
@markocikos thanks for bringing this, I think we don't need to define event.preventDefault() or anything else, I think we can just switch to using <ClayButton/> in <ClayCardWithHorizontal/> it will solve the problem or just set the type to button, without it, a button will trigger the submit form.
@matuzalemsteles we probably wouldn't have had this issue if we used ClayButton instead of button since we default the type to "button". ๐ ๐ ๐
Might be a good opportunity for us to re-evaluate our uses of <button> throughout clay to make sure we always have a default type.
@bryceosterhaus yeah ๐, we probably missed something while we were building the components in the beginning and we weren't using our own components ๐ or really some were not yet ready ๐คทโโ๏ธ
I will close this. Fixed by #3794 and #3795.