It stops working when the instances are nested in a component.
It stops working when the instances are nested in a component.
Hi @PwT, Thanks for flagging this! I appreciate you sharing the recording and the file, it helps a lot!
I notice that the components āButtonā, āOption 1ā, āOption 2ā, and āComponent 1ā are all interactive components with hover interaction.
In such case, Iāve conducted some tests on my side and observed a similar behavior, which unfortunately seems to be linked to a long-standing bug. Iāve added your case to the related tracking report internally to keep working on this issue.
However, if I detached the instance it appears working normally. Could you please try detaching the instance for āComponent 2ā in Frame 2 and see if that applicable as a workaround for your prototype?
I hope this clarifies things a bit. Thank you for your understanding in this matter. Additionally, if anyone in our community has any other workarounds, please feel free to share here.
Thanks again for your input.
Hi @Junko3 , Thank you for replying!
Detaching the instance does work but I need the instance attached in my other project as the second component has variants.
Iāve made another video to better demonstrate what I need and it has led to me finding out that the hover state also wouldnāt go away when the āReset component stateā is selected.
Hi @PwT, Thank you for checking the detach instance and it ās unfortunate that workaround wouldnāt work for your design. Also, I appreciate you sharing the additional information with us!
While weād love to give you an estimated time for resolution, unfortunately, weāre unable to do so at the moment. We appreciate your understanding.
In the meantime, if anyone from our community has any workaround for this, please share here!
Thanks,
Hi @Junko3 , Thank you for your help anyway!
1 Like