Forum Discussion

LindseyBall-0fc's avatar
LindseyBall-0fc
Community Member
6 months ago

Button not appearing on layer for some users

Hi all, looking to see if anyone has experienced something similar. I have a simple single-select question slide, using a Question layout. For some mobile users, when they answer the question and click Submit, the Correct or Incorrect layer appears with the state changes on the respective layer, but the button on the layer does not appear. There is no trigger or anything to have the button appear; it's an object that lives on the layer timeline, no intro or outro animation or anything. The button jumps to the next slide when clicked, so when it doesn't appear, the user is stuck on the layer. I do not use the built-in player controls for this slide, but do use the Button item with no custom states (just the built-in ones). Has anyone seen this and been able to fix it? Could it be due to the age and capabilities of the user's phone? This specific user is viewing the module in Japanese, but I do not believe it is an issue isolated to character languages, because I have received feedback on this from a few other drivers viewing the English version. This specific driver now has four courses behaving the same way, and I am not able to reproduce myself. Thank you for any tips!

4 Replies

  • Nedim's avatar
    Nedim
    Community Member

    Would you mind uploading the slide in question so more people can test it out? Or possibly a link that can be tested directly in the browser?

    • Nedim's avatar
      Nedim
      Community Member

      I wasn't able to replicate this behavior. I tested it on several mobile devices and browsers, both on SCORM Cloud and my own server. In all cases, the Continue button appeared, and I was able to proceed to the next slide.

      I also reviewed your setup and didn't find any major issues, except that your master feedback layers are fully transparent and contain no objects and placeholders. However, I don't believe that's the cause, as it seems to be an isolated user issue.

      One thing to check: were the users who reported the problem at least able to see the Submit button on the base layer (positioned just below the Continue button on the feedback layer)? If that's the case, the button might be serving a dual purpose: first to submit the interaction, and then to jump to the next slide once the interaction is complete. However, I wouldn't recommend trying to tweak that behavior right now, since it appears to be an isolated issue affecting only a few users.

      Instead, I suggest gathering as much information as possible from those users, such as the browser they're using, the mobile device model, network conditions, and so on.

      It may also be worth submitting a case to Articulate Support so they can test it further and help rule out any platform-specific issues.