Skip to main content
patrickz95336299
Participant
May 24, 2016
Question

Drag and drop issue HTML5 preview & publish (bug?)

  • May 24, 2016
  • 1 reply
  • 334 views

Hello,

i don't know if that's a bug or if i am missing some options, but i have a *weird* behaviour when building a drag and drop in Captivate 9(latest version).

So here what i build: (1) I have a drag and drop slide. 2 sources and 2 targets. (2) Only one of the target is accepted, for each of them. (3) I send the sources back to original position if it is the wrong target. (See the images for clearer understanding.)

(1) (2)

(3)

And here what's going wrong:

Now when i preview it in HTML5 and i drag the source to the wrong target, it snaps back, and if i try to drag it again very quick i can't grab it. But if i wait 1 or 2 seconds it will work! The weird thing is, if i drag it somewhere else (anywhere except the targets) and try to grab it again very quick, i can grab it instant!

I used simple smartshapes, but the same goes for images.


So, i looked up the elements in my console but it seems that i can't figure it out why that's happening. My colleague has the same behaviour with his Captivate.
I tried it in every major browser. Always the same.

So is someone else having this problem? If you have some free time please check, if you can replicate that issue.

I think it's annoying for our costumers and users....

Thanks in regard!

This topic has been closed for replies.

1 reply

Lilybiri
Legend
May 24, 2016

Did you try to publish and check after uploading to a webserver or a LMS? The Preview HTML in Browser is not always showing exactly what will happen after publishing.

You are on CP9, is it 9.0.1.320?

patrickz95336299
Participant
May 24, 2016

Hey, thanks for responding.

I get the same behaviour when i publish it. I just tried it to be on the safe side with a published SCORM version in the SCORM cloud.

I'm using the version 9.0.0.223 and my colleague the patched version 9.0.1.320.

Maybe to make it clearer: The functionality behind it definitely works. I just can't figure out why there is this "grabbing-lag" between the resend target and non-target. Were you able to replicate that behaviour?

Lilybiri
Legend
May 24, 2016

Yes, I can reproduce that issue. You should log a bug.