-
Notifications
You must be signed in to change notification settings - Fork 2
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
Event slotchange not triggering for react vdom #205
Labels
Comments
rmenner
added a commit
that referenced
this issue
Nov 15, 2024
6 tasks
rmenner
added a commit
that referenced
this issue
Nov 15, 2024
rmenner
added a commit
that referenced
this issue
Nov 15, 2024
rmenner
added a commit
that referenced
this issue
Nov 16, 2024
rmenner
added a commit
that referenced
this issue
Nov 20, 2024
rmenner
added a commit
that referenced
this issue
Nov 20, 2024
rmenner
added a commit
that referenced
this issue
Nov 20, 2024
rmenner
added a commit
that referenced
this issue
Nov 20, 2024
blackfalcon
pushed a commit
that referenced
this issue
Nov 20, 2024
# [2.2.0](v2.1.4...v2.2.0) (2024-11-20) ### Bug Fixes * convert slotchange event to MutationObserver [#205](#205) ([07b8455](07b8455)) ### Features * update auro-library to 3.0.1 ([89d6335](89d6335)) ### Performance Improvements * refactor mutation observer logic [#205](#205) ([877f3d7](877f3d7)) * simplify the default slot query selector [#205](#205) ([dcab4e0](dcab4e0)) * sourcery sugested refactor to reduce complexity [#205](#205) ([a81a9f2](a81a9f2)) * update library to 3.0.2 ([f34709b](f34709b))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please verify the version of auro-combobox you have installed
2.1.4
Please describe the bug
Use react to update menu items from slow api call in combobox
Reproducing the error
This issue cannot be reproduced on the Auro docsite
Expected behavior
dropdown menu should open when new items load
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Additional context
No response
Exit criteria
No response
The text was updated successfully, but these errors were encountered: