Forum Discussion

SamClark's avatar
SamClark
Community Member
7 years ago

IE Edge - Jump to next slide

A customer is running a course published in SL 360 back in December 2016. Reported that IE edge doesn't proceed to the next slide when clicking a button with an associated trigger.

We tested ourselves in both IE Edge/Win 10 and Chrome/Win 7 and found that IE Edge does nothing clicking the button while Chrome proceeded as expected.

We will try republishing with current SL 360 to see if this resolves the issue.

Anyone else seeing problems in IE Edge?

Sam

7 Replies

  • Hi there, Sam. I'm happy to help!

    Out of curiosity, is this issue related to the locking one you mentioned in this discussion? Fingers crossed republishing on the latest version of Storyline 360 did the trick! 

    If it isn't related, mind letting me know the affected slide(s) and sharing the .story file with me? I'd like to run some tests in different environments.

    Simply pop it into this discussion by using the Add Attachment link in your reply, or share it privately with me here. Looking forward to lending a hand!

  • SamClark's avatar
    SamClark
    Community Member

    I thought I posted back here.  We republished with the current SL 360 and it resolved the issue in IE Edge.

    Sam

  • FannyMaroto's avatar
    FannyMaroto
    Community Member

    Hello! Are there any compatibility issues with Internet Explorer? We are getting files corrupted every time an user attempts to complete a course using this browser.

    I will truly appreciate any assistance. Thank you!

    • LaurenDuvall's avatar
      LaurenDuvall
      Staff

      Hello Fanny!

      There aren't any compatibility issues with Storyline and Internet Explorer, but you might be using an LMS that recommends using another browser.

      If you have a screenshot of the error message, we should be able to point you to the right spot for help!

  • FannyMaroto's avatar
    FannyMaroto
    Community Member

    Thank you! Please see a screenshot attached. The error is showing in Internet Explorer, the same file doesn't seem to be corrupted in any other browser.