Open marlon-tucker opened 7 years ago
Same issue here. any clue about this issue?
I think I disabled pointer events via css and that sorted it
On Tue, 25 Sep 2018, 18:18 webcat_black, notifications@github.com wrote:
Same issue here. any clue about this issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bleenco/ngx-uploader/issues/340#issuecomment-424426829, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHOQ-zzG-h7QqEzM2S0nUM_seIvb1GBks5uemVbgaJpZM4PX2HS .
Yeah. it works fine, but I can't give a pointer-events: none
to all child elements, that's why some of them are links and some of them are buttons and so on. Any better solution for this?
Sorry that was the solution that worked in our circumstances, I didn't investigate further after that.
Though on the initial Drag event you could enable a class which disables pointer-events, and then remove the classs either on drag out or on drop complete.
The user won't be wanting to interact with any child elements during a drag / drop action.
On Tue, Sep 25, 2018 at 7:15 PM webcat_black notifications@github.com wrote:
Yeah. it works fine, but I can't give a pointer-events: none to all child elements, that's why some of them are links and some of them are buttons and so on. Any better solution for this?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bleenco/ngx-uploader/issues/340#issuecomment-424447607, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHOQz_sdY5-IfUZ-g-YHbGbFTxIk0SKks5uenLVgaJpZM4PX2HS .
That could be an option. Thank you very much for your help
Hello,
On chrome, the drag out event fires when the user goes over elements which exist inside the drop area, therefore causes horrible flicker depending on what the drag over styles are.
It can be replicated on the demo page using Chrome Version 61.0.3163.79 (whatever the latest is).
I reckon confirming the event target is the same as the element where the directive is declared will resolve this problem - but that's just a guess.
Thanks
Marlon