Check / Tick marks in the menu

May 06, 2021

These seem to have appeared in a recent update? I certainly don't remember them being there before.

Can they be turned off?

38 Replies
Developer Ignition

Even when a slide contains a graded question, a tick appears in the menu as soon as the user lands on that slide. I'm sure you can appreciate that it could be more helpful if the tick only appears once the question has been answered, and optionally, only once it is answered correctly.

I believe the same reasoning is valid for any other slide. It would be helpful if the content author can decide when a page is complete, and therefore control when a tick appears in the menu.

Furthermore, a side-effect of the current behavior is that a user can "cheat" and mark all pages as complete by simply clicking down the side menu, without completing any interactions on the page.

Finally, it would be extremely helpful if Storyline could contain built-in logic to mark the page as complete only after all applicable objects on the page are displaying their "visited" state - i.e. when an author creates a "visited" state for an object, Storyline automatically begins "watching" that object as a condition for when the page is marked as complete.

Liz Elm

I'd like to throw my voice into the request for these features as well. Our students find the current menu checkmarks incredibly confusing.

Additionally, in Storyline, the ability to prevent users from submitting their exams/quizzes until all questions have been answered was removed, (although it's a feature in Studio 360 Quizmaker settings). No matter how many warning screens and instructions we put into our exams, students still think they're answering everything because of these menu checkmarks. 

Please consider bumping this up on the list of updates requested.

Thanks guys. 

Moritz Weber

You can also add a trigger "Execute JavaScript" on the first slide of your project with code:

var styleScript = document.createElement('style');
styleScript.type = 'text/css';
styleScript.innerHTML = ".cs-icon.check-icon { display: none !important; }";
document.head.appendChild(styleScript);

Then you don't need to patch the .html everytime you create a new export.

Liz Elm
Moritz Weber

You can also add a trigger "Execute JavaScript" on the first slide of your project with code:

var styleScript = document.createElement('style');
styleScript.type = 'text/css';
styleScript.innerHTML = ".cs-icon.check-icon { display: none !important; }";
document.head.appendChild(styleScript);

Then you don't need to patch the .html everytime you create a new export.

This works GREAT. Thank you Moritz! 

Moritz Weber

I'm glad you figured it out!

I have a solution, but I'm afraid it's not the most elegant one. If you copy the JavaScript trigger to all slides or all master slides instead of the first slide of your project, then it will work every time you continue the WBT. But even as a JavaScript layman, I suspect that the same line of code will be inserted into the HTML on every slide that the user visits. That shouldn't be a problem in terms of performance - but I think a conscientious developer would shake their head :D

I hope this helps you.

Moritz Weber

Update: With this code on every master slide it should work "elegant":

if (!document.getElementById('hideTicks')) {
    var styleScript = document.createElement('style');
    styleScript.type = 'text/css';
    styleScript.id = 'hideTicks';
    styleScript.innerHTML = ".cs-icon.check-icon { display: none !important; }";
    document.head.appendChild(styleScript);
}