Sidebar not hiding when entering from hompage's Next steps

[jinchuika]

Branch: master
Build: 0.15b2 (installed from PPA)
Expected behavior: Clicking on one of the Next Steps links should show the exercise after hiding the sidebar.
Actual behavior: The sidebar doesn't hide when you enter to the exercise via Next Steps. The exercises is loaded and you can hide the sidebar after.

[MCGallaspy]

I can't replicate this. The sidebar closes fine for me. However, I encountered another (possibly related) issue, where the "Next Steps" card links to a topic instead of a content item, so that the sidebar simply is open to that point and no content is loaded.

[rtibbles]

Part of the next steps card links to a topic, part to the content, so that is intended behaviour, @MCGallaspy.

[MCGallaspy]

All of my next steps cards lead to topics.

Contrary to my expectations, clicking the "topic" icon leads to the same topic for all of them: /learn/khan/math/early-math/. I expected clicking the "topic" icon to lead to the content item.

Clicking the name of the item leads directly to that item. If this is expected behavior, please close the issues @rtibbles.

[radinamatic]

I was also unable to replicate the original issue 0.15 (Ubuntu & Windows). I have a vague memory of this being fixed at some point, but can't find the respective PR.

So, clicking the title of the item leads to the item itself (video/exercise), clicking the Topic (arrow icon) opens the sidebar leaving the user to select one item from that topic.

The only thing I find might be confusing to the user is if they decide to close the sidebar at that point, and end up on a completely blank page. Wouldn't it be better for contentrec to remain "active" behind the sidebar, until the user actually chooses one item from it? Right now content recommendation page seems to "disappear" while the sidebar is loaded...

[MCGallaspy]

@radinamatic you raise some good points. Closing this issue because the original seems to be resolved, but perhaps we can re-open some new issues/feature requests from the above discussion.

[rtibbles]

I think this issue has now genuinely been resolved by #4923 also.