Cannot disable swipe

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)

16 Replies
Rena Maguire

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!

Leslie McKerchie

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.

Rena Maguire

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

Giulia Negro

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

Katie (Gokhshteyn) Riggio

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!

Giulia Negro

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

Maureen Matsumoto

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

Leslie McKerchie

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.