Forum Discussion
Exit button obscures navigation on mobile browsers
I'm really struggling with the Exit button feature on all mobile browsers and I'm launching a custom LMS for a top tier University in 16 days.
Unfortunately, the EXIT button blocks the "previous lesson" button on all mobile devices. No matter how the button is configured (full width or floating) in the Rise theme, it overlays and makes it impossible to use the "previous lesson" button. Is there anything we can do in our custom LMS to overcome this issue?
The Exit button should not overlap the previous lesson button on mobile browsers. You can adjust the positioning using CSS or reduce the button's size for mobile screens. If needed, you can also use media queries or JavaScript
blockbenchI cannot see where my dev team is able to affect the "EXIT" button using CSS in the template on Rise360. It is added during the export stage as an add-on, with no ability to customize except the label name, that I can find. It is not feasible for us to edit each CSS file individually once it's downloaded, if that's what you mean. Is there a way to ask my dev to automatically prep the file as it is uploaded, for every file to accomodate for this?
What we were hoping to achieve directly in the template so we do not have to adjust a file post-export:- Add margin above the "go to previous segment" link so that there's white space on top of it - that way the container with the "EXIT" button will occupy that white space and not obstruct the link.
- Split the container with the "EXIT" button so that it's not a single container containing both the "hamburger menu" on the left and the EXIT button on the right - rather make it two separate containers containing each of these 2 elements, and position them on the top, but opposite ends horizontally. That way, the hamburger menu will be in the top-left corner, the EXIT button will be in the top right corner, and the area in between will not be obstructed and so the "go to previous segment" link will be visible.
The ideal solution would be for your dev team to find a way to preprocess the CSS or HTML during the export process to handle these customizations automatically. Depending on how Rise360 handles exports, this may involve adding custom preprocessing steps or modifying the export configuration.
Unfortunately, if this level of customization isn't available directly through the Rise360 interface, the best option might be to focus on an automated process to edit the exported files consistently.
