Cannot disable swipe
Sep 10, 2018
By
Rena Maguire
While struggling to find a workaround with a potential bug in Storyline 360 (https://community.articulate.com/discussions/articulate-storyline/next-layer-showing-unexpectedly-on-mobile#reply-547424), I think I have discovered another bug. When I disable the "Swipe Next" and "Swipe Prev" buttons in the Slide Navigation controls, I am still able to swipe while testing on my mobile. If I disable both Swipe and Buttons, I am no longer able to swipe.
I have attached the test storyline file. It was tested in Chrome on:
Samsung A5 using Android version 8.0.0
iPhone 6s iOS 11.4.1 (15G77)
48 Replies
Sorry to bump this, but I have a meeting scheduled for Monday to discuss how we should move forward on these two issues that have been identified. The first bug we discovered means that users are accidentally swiping to the next screen, and this bug means we can't disable swiping to prevent that. We have issues with all our courses going back as far as those published in May, so implementing a workaround will be time consuming. Is anyone else having these issues, and will a fix be available soon? Thanks!
Thanks for checking in, Rena. I don't have an ETA on a fix for those bugs just yet, but we'll be sure to let you know as soon as we have more information. Here's an inside look at how we prioritize and tackle bugs -- we'll keep you posted!
Any news? It's been over a month, and we still have several courses stuck awaiting publication after these bugs are fixed.
Hey Rena,
No update yet and it looks like Alyssa shared how we prioritize bugs above.
Did you try the suggestion that Anna shared with moving the layer content to a new slide to avoid the issue you are seeing?
This conversation is attached so that we can update you both here and in your support case when we are able.
Hi Leslie,
That's too bad. Anna's suggestion does not work for us. Oftentimes we use
that layer to give visual hints as to what the user needs to do, such as
highlighting the parts not selected, etc. The suggestion would not allow us
to do that, and also would break the style we have chosen for our courses.
This problem affects several of our projects, but we also have many more
previously published courses that work fine the way they are. We are
pursuing other options for how to solve this problem. In the meantime, I
would appreciate any updates you get on this issue.
Thanks,
Rena
Hello!!
I'm facing the same problem on courses made of a huge amount of hours....by the way we're suggesting our users to use Puffin Browser only, this because we still use the flash/html5 player (as Puffin read well Flash contents) even if they're still able to open it on other browsers and swipe slides.
As the large amount of slides I cannot change a lot of settings or variables on slides so I hope this bug will solved soon.
Thanks,
Giulia
Hi, Giulia. Thanks for reaching out!
I'm so sorry for the trouble this bug is causing, and I can appreciate that the workaround you've found isn't ideal. Would you be able to share your .story file with our Support Engineers? We'll do our best to find other approaches that do not alter the design – here's the upload link if you can share the project. 🤞
We'll keep you in the know with any new information on this bug, too. Let us know if you have any more questions!
Thank you Katie!
Here's a sample of our courses with variables set, I tried even to unable the Articulate Mobile Player but it seems not changing anything on the smartphone view.
Would be great to unable certain browser app (such disable Chrome and Mozilla, and able Puffin) but we did something similar previously changing the LMS settings
Thanks, Giulia. I've attached this conversation to our report of the issue as we track user impact and so we can update you here when we can.
I did want to mention that Puffin is not a supported browser as you can see in our system requirements here.
I am also experiencing the inability to disable the swipe on Next and Prev. My clients are OK as long as it is on a desktop platform, but they are upset that mobile users can blow through a course by swiping. Tested on Galaxy and iPhone platforms with the same result.
Hi Will,
I'm sorry this bug is causing a snag for you too. Our team is still looking into it, so once we have an update to share please know we'll post in this discussion.
Hi Ashley,
Is there an update for the inability to disable the swipe on Next and Prev?
If not, has anyone figured out a workaround? I think I have the same problem as everyone else in this post and two other posts, but if not, here is our scenario:
A slide begins with the Next button hidden when the timeline starts. The learner must interact with a slide before the Next button's state changes to Normal. The learner is able to swipe to the next slide without interacting with it.
Thank you for your help!
Maureen
Hi again,
I have the same issue as others, if I turn off swiping in the player on each slide, I can still swipe.
Hi Maureen,
Thanks for reaching out and sharing what you are experiencing in your course as well.
Is this happening after a few swipe attempts? I do see a similar issue reported where swiping works even when navigation is set to restricted and there is no swipe trigger enabled on the slide. The steps to replicate state 'after a few swipe attempts', the course moves to the next slide.
If confirmed, I'll add this conversation to the report.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
Hi Leslie.
Yes, that is correct. Everything is disabled and we can still swipe through a course and it reports completed to our LMS.
Thank you!
Maureen
Thanks for confirming, Maureen.
Hi All, Has the bug mentioned in this thread been fixed? I am testing a course which has swipe next disabled on slides yet I can still swipe through when testing on my samsung galaxy S7. I have even tried a work around that allowed swiping or clicking next based on the timeline finishing but I was still able to swipe next before the timeline ended.
I am feeling the frustration of everyone above in this thread.
Hi Jared,
I am sorry that you are hitting this snag as well. Our team is continuing to investigate the issue, and I am adding your comments to our report. As soon as we have an update to share, we will be sure to reach out to this thread.
Is there a work around for this? I want to be able to put a trigger on a master slide to prevent users from swiping forward without having to copy a "complete slide" Layer trigger to every slide individually.
Best Regards
Jared Nelson
E-Learning & Content Creation
Hi Jared,
Thanks for reaching out, and unfortunately, we don't have a workaround for this bug currently reported. I understand your frustration and will be sure to include your comments in the report.
As Vincent mentioned, we'll pop back in here as soon as we have any progress to share.
Hi all, So I found a kind of work around that helps me have a set of master slide triggers with layers and button to catch the "cant disable swipe bug"
I have attached a demo of this. Please note any story slides using master slide triggers for previous/next buttons cannot have triggers for these buttons in the story slide as they take preference.
Hope this helps some peeps.
Hi Jared - I would love to see your workaround, but I don't see anything attached to your post. Can you re-post it? Thanks!
Here it is, I hope this saves you the day or so of trial and error I went through. Haha. I learnt a lot about triggers though
Like I say it is not an ideal workaround but it prevents the swipe forward and it saves me copying and pasting too many triggers across slides.
Thanks, Jared. We have also considered creating our own player buttons to get around some of the issues we have experienced with bugs, but ultimately are still hoping this issue gets resolved.