Chrome support for Flare WebHelp
Chrome support for Flare WebHelp
For the most part, the output generated from Flare 5.01 seems render and behave correctly in Google Chrome. The exception is the "Back" button seems to reload the original Default.htm in the root rather than backing up to the previous page loaded in the frame. I assume this is a Google Chrome issue rather than an issue with the HTML generated by Flare. Correct?
Re: Chrome support for Flare WebHelp
We've just discovered this issue as well - the Back arrow, which functions correctly in IE, returns to the default start page if you navigate a number of topics using the TOC or if you click an external link in a merged webhelp system.
Does anyone have a fix/workaround for this?
cheers
Dan
Does anyone have a fix/workaround for this?
cheers
Dan
-
Paul Griffiths
- Sr. Propeller Head
- Posts: 262
- Joined: Wed Apr 18, 2007 2:25 am
- Location: Nottingham, UK
Re: Chrome support for Flare WebHelp
I'm still seeing this in Flare 7. A workaround woudl be useful, if anyone has any ideas?
UPDATE: It seems that the Back button does not work on any topic that has been opened from a related topic link that has been inserted via a relationship table. It’s fine on any topic opened from the TOC, Index or Search, and the problem does not occur on other projects that do not use relationship tables to define their related topics. IE and FireFox do not exhibit the problem either.
I've raised a Support ticket.
UPDATE: It seems that the Back button does not work on any topic that has been opened from a related topic link that has been inserted via a relationship table. It’s fine on any topic opened from the TOC, Index or Search, and the problem does not occur on other projects that do not use relationship tables to define their related topics. IE and FireFox do not exhibit the problem either.
I've raised a Support ticket.
-
Paul Griffiths
- Sr. Propeller Head
- Posts: 262
- Joined: Wed Apr 18, 2007 2:25 am
- Location: Nottingham, UK
Re: Chrome support for Flare WebHelp
FURTHER UPDATE: MadCap have confirmed this as a bug.