TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Google Chrome 9.0.597.84 still broken for WebHelp
Subject:Re: Google Chrome 9.0.597.84 still broken for WebHelp From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Rédacteur en chef <editorialstandards -at- gmail -dot- com> Date:Mon, 7 Feb 2011 14:49:05 -0500
I've seen nothing new other than new comments from other frustrated
tech writers in their bug base. Publicly served WebHelp (and similar)
systems with "Does not work with Google Chrome" disclaimers/error
pages might be the way to go. HAT vendors are now all
releasing/working on new formats, in part because of this very issue.
2011/2/7 Rédacteur en chef <editorialstandards -at- gmail -dot- com>:
> All,
>
> I think the last time I noticed, Chrome was at 8-dot-something, and
> it was broken for WebHelp.
>
> I make it a point to try my help on all the big browsers as each
> of my projects comes around toward its release date.
>
> Chrome appears to have updated itself to 9.0.5...., and it is still broken
> for WebHelp.
>
> I doubt that all the other browsers - which work perfectly fine with
> WebHelp, so far, are leaving a huge security hole unplugged, so
> I'm refusing to say that WebHelp is broken. It's Chrome's fault.
>
> If there was a problem, then the other browsers have addressed
> it by now, in a fashion that doesn't preclude WebHelp.
>
> There were rumors that Google was addressing the problem since
> version 8-dot-something was in Beta, and now we're at 9.0
> released/stable version, so it seems fair to say that either
> Google has no intention of fixing the problem that they made,
> or else no capability to do so.
>
> I've got a hundred bucks here that says somebody at Google
> used the nefarious power of the all-groping Google tentacles
> to check how many instances of "WebHelp" were actually
> ON the Web, and decided that the number was too small
> to bother with.
>
> Of course, most instances of WebHelp won't BE on the web.
> They're on company servers, protected by logins, or (like
> mine) they're stand-alone on CDs and on hard disks of
> product users.
>
> I... ahem... Googled for a workaround, but didn't see
> anything I'd want to tell my customers, so I'm continuing
> to include a Readme.txt that says "... WebHelp viewable in
> any modern browser, except Google Chrome".
> The only workarounds I've seen suggested on the Flare and
> RoboHelp forums have been worse than the problem.
>
> Of course, I can't add snarky little readme files to
> the past 10 years of product that's already out there,
> so those customers will need to learn the hard way.
> Anybody who's had a product for ten years is usually
> looking at the Help _only_ in a situation where something
> has gone wrong and they need to sort it out quickly.
> It also doesn't help that Chrome worked fine with WebHelp
> for many releases prior to 8-dot-something-or-other.
>
> Has anybody seen anything useful or amusing on this topic?
>
> </kevin>
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-