We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug (required)
I am trying to use SPA combination with my application hence i need to use my child app inside shadow dom to avoid any changes in parent app.
My application drag drop completely stopped and not able to drag.
This is really required to match with current UI apps as multiple apps moving towards Single page apps
To Reproduce (required)
Steps to reproduce the behavior:
Any application inside shadow dom will not allow to drag/ drop
If your issue appears in a larger codebase and it you can't pin down why it is happening, please
URL with basic example : https://stackblitz.com/edit/angular-17-starter-project-e8arvi
Screenshots (optional)
NA
Versions (required)
@angular/core
ng2-dragula
Browsers affected (optional)
Chrome latest
Additional context (optional)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug (required)
I am trying to use SPA combination with my application hence i need to use my child app inside shadow dom to avoid any changes in parent app.
My application drag drop completely stopped and not able to drag.
This is really required to match with current UI apps as multiple apps moving towards Single page apps
To Reproduce (required)
Steps to reproduce the behavior:
Any application inside shadow dom will not allow to drag/ drop
If your issue appears in a larger codebase and it you can't pin down why it is
happening, please
URL with basic example : https://stackblitz.com/edit/angular-17-starter-project-e8arvi
Screenshots (optional)
NA
Versions (required)
@angular/core
: 17ng2-dragula
: 5.1.0Browsers affected (optional)
Chrome latest
Additional context (optional)
NA
The text was updated successfully, but these errors were encountered: