Compatibility with Dragula
See original GitHub issueDragula Drag&Drop library: https://github.com/valor-software/ng2-dragula
The problem:
<div dragula="my-bag" virtualScroll...>
<list-item />
</div>
Generates:
<div dragula="my-bag" virtualScroll...>
<div class="total-padding" />
<div class="scrollable-content>
<list-item />
</div>
</div>
I think that being able to put the [dragula]
attribute on the div.scrollbable-content
would fix the Dragula functionality.
Is there any way to put certain classes/inputs etc on the .scrollable-content?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7
Top Results From Across the Web
ng2-dragula versions and peer dependencies
Online Peer dependency version tool to search for compatible versions of related NPM packages.
Read more >ng2-dragula | Simple drag and drop with ... - Valor Software
Drag and drop so simple it hurts. Note: these examples mimic the ones for dragula , but using ng2-dragula . Move stuff between...
Read more >ng2-dragula - npm
Simple drag and drop with dragula. Latest version: 3.2.0, last published: 19 days ago. Start using ng2-dragula in your project by running ...
Read more >Dragula/Angular: How to allow draggable items to be dropped ...
I am designing a web app in Angular with dragula included in my project. It works just fine for dragging and dropping things...
Read more >The Boulet Brothers Reach New Heights ... - Shore Fire Media
THE BOULET BROTHERS' DRAGULA” FRANCHISE IS THE MOST WATCHED SERIES ON SHUDDER SINCE “TITANS” PREMIERE IN OCTOBER CASTING FOR.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@samsamm777, if you add #container to your component with the *ngFor it should fix the issue where not all of the components displayed. This worked for me, hopefully for you too.
Closing as shohrukh92 has suggested a workaround.