Hi,
I have a project which outputs to HTML5 Side Navigation. Each time I click on an item in the TOC, the entire webpage, including the TOC itself, refreshes. Is there anyway to prevent this?
Thanks in advance!
HTML5 Side Navigation Refresh Issue
-
techwriter31
- Propellus Maximus
- Posts: 551
- Joined: Wed Mar 05, 2008 10:50 am
Re: HTML5 Side Navigation Refresh Issue
We found this to be a problem too. While it doesn't fix the refresh issue, setting the side navigation background color to white made it less noticeable.
Last edited by techwriter31 on Mon Oct 22, 2018 6:15 am, edited 1 time in total.
Kellie
Re: HTML5 Side Navigation Refresh Issue
Thank you so much. I'll try it out!
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2650
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: HTML5 Side Navigation Refresh Issue
I'm experiencing this too. It seems particularly noticeable if the page content is longer than the space allowed, as it then has to insert a scroll bar.
Other than changing the background colour of the sidenav (mine is already white) does anyone have any suggestions how to deal with this? One potential solution that popped into my head could be to smooth the transition when you click the Next topic and Previous topic buttons, but I don't know how to do that, I suspect I'd need some javascript and it's not one of my skills.
Other than changing the background colour of the sidenav (mine is already white) does anyone have any suggestions how to deal with this? One potential solution that popped into my head could be to smooth the transition when you click the Next topic and Previous topic buttons, but I don't know how to do that, I suspect I'd need some javascript and it's not one of my skills.
Started as a newbie with Flare 6.1, now using Flare 2024r2.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: HTML5 Side Navigation Refresh Issue
I'd like to be proven wrong on this, but I don't think there's an easy way to completely fix this - you'll still see the menu being filled with items.
You could fix it using a bit of javascript and CSS - although I appreciate not everyone will be able to do this.
A while ago, MadCap added "loaded" events, so you can tell when the menus have finished loading.
http://kb.madcapsoftware.com/Content/Mi ... _Menus.htm
This also appears to work for the side nav menu; e.g.
So for example, you could hide the menu content by default (e.g. add a class to the menu item using jQuery, and set the class CSS not to display), then when the side nav menu has loaded you could show the menu (e.g. remove the class that you added). And you could incorporate CSS transitions to make it smoother, e.g. fade in.
You could fix it using a bit of javascript and CSS - although I appreciate not everyone will be able to do this.
A while ago, MadCap added "loaded" events, so you can tell when the menus have finished loading.
http://kb.madcapsoftware.com/Content/Mi ... _Menus.htm
This also appears to work for the side nav menu; e.g.
Code: Select all
$(document).ready(function(){
$(".menu.sidenav").on("loaded", function () {
console.log("side nav loaded!");
});
});Re: HTML5 Side Navigation Refresh Issue
Does MadCap have any plans of improving the behavior of these pages? Even the page header is getting reloaded on every click in the nav pane. This is a bad user experience - it feels like using an HTML page from the 90s.
Re: HTML5 Side Navigation Refresh Issue
Although MadCap staff do come here now and again, this is a peer-to-peer forum, so you're unlikely to get an answer.tjl wrote:Does MadCap have any plans of improving the behavior of these pages? Even the page header is getting reloaded on every click in the nav pane. This is a bad user experience - it feels like using an HTML page from the 90s.
So you could try asking MadCap directly, or maybe put in a feature request.
I'm not aware of any significant changes to page rendering since this was posted in 2018.