States and triggers appear to have a dependency on browser

Hello everyone,

I have a story in which I'm allowing my audience to click on various images to progress through an e-learning course.  I have several states defined for each image, changing their state from normal, to selected (image shows with an outline when hovering cursor), to visited (image shows as grayed-out once they click on an image) depending upon their actions.  Once the user has clicked on (or visited) all images, I use a trigger to switch that slide to a different layer, thus officially ending the course.  I've published this story to two formats, CD and LMS, for testing.  And I've tested each of those formats using 3 browsers, Chrome, Firefox, and Microsoft Edge.  I'm getting very erratic behavior from the states, regardless of the published format, with Firefox being the worst, followed by an occasional occurrence in Chrome, and I've yet to see it in Edge.  Here's what happens...The "selected" state functions flawlessly when hovering cursor in all browsers.  However, the visited state almost always shows as selected in Firefox.  This means that even though a student has visited all images, all those images show in their selected state, and thus the slide never changes to the desired layer, and the course never officially ends.  In this situation, I find that if I revisit each image, then the state appears correctly, and the course ends.  Another thing I've seen is that if I run through the course once, experience the erratic behavior, if I close the course, restart it, and run through it again in the same browser, it might function properly.  I can't control which browser my students are using, so I'm really unsure what I can do to fix this issue.  Is this a Storyline issue or a browser issue?

Thanks,
Matt