-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search Input Triggers Dropdown #1340
Comments
this 'bug' can be reproduction with 'any way'if you put a 'any component' before dropdown.the dropdown will be triggers when you click 'any component' how to standard use 'Dropdown' ?there was a 'Button' component before default 'Dropdown'. why ?the sample from dropdown examples guess what you needmaybe that's what you want input suggestion. flowbite-svelte seems to be based on flowbite so you have to work for yourself and referring to the source code of antdesign may help you |
I think what you're trying to say is I'm using the component wrong. Assuming that's what you're trying to say, I'll just say that either the Search input is tripping the dropdown's event handler, or the dropdown's bind:open is not being honored. Here's where the examples show bind:open is supposed to be honored: https://flowbite-svelte.com/docs/components/dropdown#Programatic_open/close |
misunderstandingyou say now I think you meanThe |
Yes! Exactly!
May 7, 2024 1:10:30 AM jumtp ***@***.***>:
…
I think what you're trying to say is I'm using the component wrong.
Assuming that's what you're trying to say, I'll just say that either the Search input is tripping the dropdown's event handler, or the dropdown's bind:open is not being honored.
Here's where the examples show bind:open is supposed to be honored: https://flowbite-svelte.com/docs/components/dropdown#Programatic_open/close
*misunderstanding*
you say *I think what you're trying to say is I'm using the component wrong*.that's i want to say.but now i get new info from you.
*now I think you mean*
The *any component* is not allow to control *Dropdown Component* show or hidden because use *bind:open={isShow}* so should use *isShow* control *Dropdown Component* show or hidden. Do I understand correctly?
—
Reply to this email directly, view it on GitHub[#1340 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACNCM6TCLNWLYAGUS7DPGWLZBBV5NAVCNFSM6AAAAABHGFWDNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGUZDCNRYGQ].
You are receiving this because you authored the thread.
[Tracking image][https://github.com/notifications/beacon/ACNCM6TWX5VGI6HCXH4QU2LZBBV5NA5CNFSM6AAAAABHGFWDNCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT5AWSBI.gif]
|
Is this a bug or feature?Need to confirm if this is a bug @shinokada The problem is from follwing code if this is a bugflowbite-svelte/src/lib/utils/Popper.svelte Lines 130 to 140 in 6ff61d2
the code make some HtmlElement has event through the 'triggeredBy' . Obviously the code executes previousElementSibling on line 131
Difficulties in solving this problem
maybe follwing code can resolve this problem (Not rigorous, not tested)
|
Describe the bug
Clicking on a Search component triggers a neighboring Dropdown to open
Reproduction
https://svelte.dev/repl/a621608feb7c401b91f137ad431cfa23?version=4.2.15
Flowbite version and System Info
The text was updated successfully, but these errors were encountered: