Tweaks for DraggableWin directive

[ntma]

Fixes:

• Support for Firefox (e.path is Google Chrome specific);
• Reset dragger offset for each mousedown event (prevents magical jumps);
• Constain floating windows to the main container; (future PR)

#252

[fschmenger]

@ntma Hi Nuno, thanks for kickstarting this! I'm currently a little limited in time but can give it a test run by next week hopefully.

Keep in mind that Task 3) will be a breaking change due to the changes in positioning offsets. Probably this should be in a separate PR, so it can be incorporated with the next Wegue major version.

[ntma]

Hi @fschmenger , no problem!

Keep in mind that Task 3) will be a breaking change due to the changes in positioning offsets. Probably this should be in a separate PR, so it can be incorporated with the next Wegue major version.

Indeed, I got to agree with that. I will take your suggestion!

[JakobMiksch]

I do not really understand the change here. Could you explain what the behavior before and after this PR is?

[JakobMiksch]

Looks fine from my side. I tested it and it does what it should.

[JakobMiksch]

@fschmenger maybe could have a look and merge if you approve.

[chrismayer]

Thanks @ntma for this. LGTM 👍 As @JakobMiksch suggested, let's see what @fschmenger says and if he approves feel free to merge afterwards.

[fschmenger]

OK, this looks good to merge. I can finally see the draggable option working in Firefox and it no longer get's confused when dragging multiple cards.

I suggest we leave #252 open, until the other topics can be addressed for v2.