-
Notifications
You must be signed in to change notification settings - Fork 8
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
🐞 - Link editor closes unexpectedly when provideAnimationsAsync()
is used
#1462
Comments
If you can reproduce it with other Taiga UI dropdowns please file it for Taiga. We do reach out to animation engine inside ActiveZone directive so that might be related. |
The code seems to just use simple
I have already debugged the code there and there is nothing there that explicitly closes the dropdown when you press the edit button. |
Opening/closing is controlled with this directive: |
Ok, I'll try to simplify the test case and see if I can reproduce it without the |
@hakimio thank you very much! |
Tried to reproduce using |
provideAnimationsAsync()
is used
@hakimio do you think we just move that issue to taiga ui repo scope? |
@splincode the issue seems to be with TuiEditorDropdownToolbar. So, I don't think this should be moved to |
Code Example URL
https://stackblitz.com/edit/angular-yqhfns-d8j69b?file=src%2Fmain.ts
Description
I have found a couple of issues in the latest version of the link editor.
A trivial one: PR fix: autofocus #1397 broke link editor's input autofocus. There is no more need to provide custom selector since(fixed)[contenteditable]
has been added upstream to the defaultquery
.provideAnimationsAsync()
introduced in Angular17
, link edit dropdown closes unexpectedly when trying to edit the link.To reproduce the second issue I have provided stackblitz demo:
This issue might be upstream Taiga UI issue. Let me know if I should open a bug report there.
Also, the issue is only reproducible on Chrome, Firefox doesn't seem to have the issue.
Taiga UI version
4.8.1
Browser Used
Chrome
OS Used
Windows
The text was updated successfully, but these errors were encountered: