DITA and XMetaL Discussion
scorho December 8, 2010 at 11:17 pm
WebHelp search results display issue in ChromeDecember 8, 2010 at 11:17 pmParticipants 6Replies 7Last Activity 11 years, 12 months ago
In Chrome, when I click a Search result, the linked topic opens without the left nav. The only way to get the nav back is to click Back until you're back where you were. Obviously this is a problem is you're trying to go through multiple search results to find your info.
It works fine in FF and IE8. Clicking a search result opens the linked topic in the content frame as expected.Su-Laine Yeo December 10, 2010 at 8:13 pm
Reply to: WebHelp search results display issue in ChromeDecember 10, 2010 at 8:13 pm
I can reproduce this issue in Chrome with the default output from WebHelp. I believe the issue is related to configuration files, as this WebHelp site http://na.justsystems.com/webhelp/en/xmetalauthor/enterprise/6.0/XMEE.html appears properly in Chrome.
If you download and install the configuration files here: http://forums.xmetal.com/index.php/topic,626.0.html , they should resolve the issue.
Su-Lainescorho December 13, 2010 at 8:02 pm
Reply to: WebHelp search results display issue in ChromeDecember 13, 2010 at 8:02 pm
Thanks for the response. I don't want to lose the customizations we've already made to the default configuration files. Is there a way to get the proper display in Chrome without completely overwriting the files we've already customized?Su-Laine Yeo December 15, 2010 at 11:12 pm
Reply to: WebHelp search results display issue in ChromeDecember 15, 2010 at 11:12 pm
I've done more testing, and there's something strange going on. Installing the customizations pack that I posted above does not fix the problem.
The problem is not seen when I access http://na.justsystems.com/webhelp/en/xmetalauthor/enterprise/6.0/XMEE.html#Welcome%20to%20XMetaL%20Author in Chrome, however it is seen if I take exactly the same Webhelp output folder that is used for the above website, and open it from the local machine using instead of from the Internet.
If you plan to distribute your Webhelp project on a web server, try your project there and it might work.Su-Laine Yeo December 15, 2010 at 11:16 pm
Reply to: WebHelp search results display issue in ChromeDecember 15, 2010 at 11:16 pm
Update: OK, a Google search for “WebHelp Chrome” got me somewhere. According to this article, the problem with web-based help on the local file system is a known issue with recent versions of Chrome, and it affects a variety of web-based help systems: http://techcommdood.com/?p=434 .
In Chrome 8, when you click a WebHelp search result on the local file system, you get the following script error:
It seems to be a manifestation of this known issue in Chrome: http://code.google.com/p/chromium/issues/detail?id=47416scorho December 16, 2010 at 4:02 am
Reply to: WebHelp search results display issue in ChromeDecember 16, 2010 at 4:02 am
Thanks! That's good to know. We've noticed a couple other minor Chrome display issues when testing locally (such as extra space after the numbers in numbered lists). Maybe they'll be fixed too. We're almost ready to test on our server. I'll try that and see if it fixes the problems.scorho December 16, 2010 at 4:06 am
Reply to: WebHelp search results display issue in ChromeDecember 16, 2010 at 4:06 am
Just noticed your update. Sounds like the same kind of issue we were seeing with webhelp generated from a different system. I'll test tomorrow and see what I see.scorho December 17, 2010 at 11:10 pm
Reply to: WebHelp search results display issue in ChromeDecember 17, 2010 at 11:10 pm
I've tested this and you're right. The nav doesn't go away when you click a search result in Chrome when the help is on the server, only when you try to test the files locally. That's very good news.
There's still one Chrome issue on our list, but it's relatively minor. Chrome throws in an extra space after a number in a numbered list, so margins aren't as neat as we'd like. Compared to the search results issue, though, this isn't that important.
- You must be logged in to reply to this topic.