Modern player navigation buttons should stick to content, not to browser window edges

I've seen other discussions on this, but the answer of "the player is responsive" seems totally off the mark. If Articulate doesn't allow us to create responsive content, then it's not really responsive, is it? Instead, we have to prescribe to users that they resize their browser window exactly right to get the previous/next buttons and the top navigation (e.g. menu/resources) in a convenient location. Then if they open the menu, everything shifts around again. PLEASE give us the ability to fix the navigation in relation to the CONTENT, not the window edges.

Shifting the buttons around the content which stays centered, is not exactly responsive. It would be so much more convenient if the navigation just stayed with the content. Please fix this, or set it as an option in the player!

Not exactly responsive

1 Reply