html elems inside v-click-outside block also recognized as outside elems

[moneyinvest]

No description provided.

[bpeab]

Also having this issue in one of our components which uses a default slot and a named slot. The issue appears only for focusable elements which are in the default slot. Focusable elements that are inside the named slot are not recognize as outside elements by v-click-outside.

[furkangkhsn]

Also having this issue in one of our components which uses a default slot and a named slot. The issue appears only for focusable elements which are in the default slot. Focusable elements that are inside the named slot are not recognize as outside elements by v-click-outside.

But why? I need an input inside a v-click-outside block. It's annoying behaviour.

[ndelvalle]

Would you guys mind investigate a bit more the issue, maybe creating something to reproduce it so it's easier to fix?
At the moment I have a lot on my plate, maybe I can take a look at it next week 🙁

[bpeab]

Of course, it's normal.

Unfortunatly, I can't share the project the issue is appearing on and I wasn't able to reproduce this issue in a blank project with the same components and dependencies. I'll try again later and come back if I found something.

[bpeab]

It was a misunderstanding.

I had a search with dropdown inside the container that had the v-click-outside directive set. The dropdown would have a variable number of elements inside of it and therefore, the container height was depending on the number of elements of the dropdown.

Clicking (mousedown) on a element of the dropdown would trigger an event and close the dropdown. By time mouseup would have been fired — which would have triggered v-click-outside — the container would have re-adjusted its height and the cursor would had endend up outside of the actual container...

It definitly not coming from v-click-outside. Sorry and thank you very much for this great library !

[ndelvalle]

@bpeab thanks for reporting back. @moneyinvest can you please provide an example that reproduces the bug?

[pepijninova]

I know this issue is quite old, but it seems like form elements with the same name are not handled how you'd expect.

I had two forms: 1 outside a modal, 1 inside.
Changing the name of the elements in the modal (_modal as suffix for example) works for us.

My guess is that form elements are checked for uniqueness using name and not parent element or something similar. I haven't looked in the code yet.