position:static? about dragdrop

[kbjr]

This has always been a requirement of the library because it uses the top and left css properties to move the dragged element; If the element has positiion: static it wouldn't go anywhere. The only change is that now it throws an error to warn you about it.

[pyrsmk]

I'm confused. I never had to change the position into absolute or relative mode with the 0.2.3 and it worked very well. Moreover, it works with this version too. I've just commented the verification.

EDIT: it seems it just works with chrome

[kbjr]

Can you show me an example of what you're doing?

On Mon, Nov 12, 2012 at 12:47 AM, Aurélien Delogu
[email protected]:

I'm confused. I never had to change the position into absolute or relative
mode with the 0.2.3 and it worked very well. Moreover, it works with this
version too. I've just commented the verification.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-10280281.

James Brumond

[email protected] | [email protected]
http://www.jbrumond.me http://www.jbrumond.me
360.713.8824

[pyrsmk]

Nope, I can't, sorry :) But, just try it with chrome, without change position:static. Anyway, you don't explain how we can use your library into your documentation (at least, with the position behavior), maybe we should update this file.

[kbjr]

Okay, I just looked back at the condition and it is (incorrectly) checking the anchor element for position: static when it should be checking the element. I will fix this as I think this is the problem you are seeing. If this is not the problem you are having, please reopen.