allowFrom doesn't work when manualStart is on
See original GitHub issuehttps://jsfiddle.net/ddenev/fvzy6mjh/
What is the proper way to specify a handle when manualStart
is on then?
@taye , please don’t ignore this and the ‘cursorChecker’ (https://github.com/taye/interact.js/issues/844) questions - I am currently blocked and need assistance/resolution.
Thank you and best regards.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Interact.js resizable and draggable not working together
draggable({ manualStart: false, allowFrom: '.handle-rotate', onstart: function (event) { console.log('onstart ...
Read more >Common Action Options - interact.js
The allowFrom option lets you specify a target CSS selector or Element which must be the target of the pointer down event in...
Read more >taye/interact.js - Gitter
i am using interact.js to drag and drop, scale and rotate elements. the problem is when i scale or rotate element, it will...
Read more >taye - Profile - Bountysource
taye commented on this issueallowFrom doesn't work when manualStart is on. interact.js 2 years ago. taye commented on this issueDocs: "Intro" page produces ......
Read more >OE8 + WSGI : CRON Not working - Odoo
Issue: https://github.com/odoo/odoo/issues/3091 I am struggling to make cron/scheduler working in Openerp/ Odoo 8 with mod_wsgi First I had problem with ...
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
@ddenev I moved my clone logic into the
dragstart
event and removed themanualStart
andinteraction.start({..})
stuff. This has the advantage of preserving my drag config (allowFrom, cursor #844 , etc…). The disadvantage that my clone isn’t associated as theevent.target
for drag events or theevent.relatedTarget
for drop events, these properties are associated to the original drag item (the trigger if you will). I’m assuming this the reason @taye made themanualStart
functionality, so that you could associate the clone as your drag item. I get around this by adding the properties I need to the element that is being dragged and reference those properties instead oftarget
andrelatedTarget
. #shamelessPlug Additionally, I’m adding this functionality to an Angular drag drop library I have published@tft/interact
. Interactive docs here. I should be able to release the new feature and update docs with example by tonight or tomorrow.The proper way is to check yourself if you want to start the action from the target element. You can use that
interactable.testIgnoreAllow()
method to check if theallowFrom
andignoeFrom
options that you set should allow the action (true
) or not (false
) before callinginteraction.start()