Firefox can't find the file at (a location is specified) when either "Navigate previous" (and next) buttons are pressed in an HTML5 skin (but OK in IE/Chrome).
I create HTML5 help projects from a package called MadCap Flare. It uses what they call an HTML5 'skin' that sets the style/layout of the page and also includes 'Navigate previous' and 'Navigate next' buttons. When viewing the help and pressing these navigate buttons in IE8 or Chrome 32 there is no problem, but in Firefox 27 I get the following: (typical error for pressing a button on any page)
"File not found"
"Firefox can't find the file at /C:/SVN/FlareEnglishOnLineHelp/Output/HTML5_Help_Modeller_Reference/4attrib/idh_jointinterface_element_meshes.htm?TocPath=Modeller Reference Manual|Chapter 5 : Model Attributes|Meshing|_____2."
" Check the file name for capitalisation or other typing errors." " Check to see if the file was moved, renamed or deleted."
- Because the files and buttons work in other browsers I'm wondering just what is going on here with Firefox>>>>
Ændret af paulblusas den
Alle svar (6)
Modeller Reference Manual|Chapter 5 : Model Attributes|Meshing|
Fix the errors in the file name = disallowed characters = : and |
Whilst that may be true (the fact that the Toc-Path entry automatically created by Madcap Flare contains : and | characters); and these characters can be seen to be the ones causing the problem since nested books in the table of contents without these characters CAN be ‘traversed’ correctly in Firefox using the ‘Navigate previous’ and ‘Navigate next’ buttons. But the fact that IE8 and Chrome display the assembled HTML5 pages correctly, regardless of the prescence of these characters, still points the finger at an apparent shortcoming in Firefox?
I should correct that last entry and state that the | charactacters are generated automatically in the Toc-Path for each 'book' name in the online help, and are not something manually created, whereas the : characters have come from the TOC book topic names (which were manually entered names and are what we would ideally require). But, because 'previous' and 'next' topics within nested TOC books without colon (:) characters CAN be browsed successfully when just | characters are present in the Toc-Path, the limitation would appear to be solely due to the : characters.
Ændret af paulblusas den
So, your problem with Firefox is solved by getting rid of the : character?
Yes.
Removing a colon (:) from a TOC book name so that (say) Chapter 2 : XYZ becomes Chapter 2 XYZ then provides browsable 'Navigate previous' and 'Navigate next' capability on all the topics within that Chapter - but only for that chapter. So Firefox cannot handle the : in TOC book names in its default 'reading' of the HTML5 pages.
I've yet to check cor-el's suggestion for getting around this as stated above.
Ændret af paulblusas den