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.
All is well after I manually upgraded to the latest Chrome browser. Both
sites had rendered AOK in other browsers, so that was the tip off. I'm not
sure why my older version of Chrome wasn't automatically updated by Google.
On Sat, Dec 17, 2011 at 4:10 PM, Tomasz Borek <tomasz -dot- borek -at- gmail -dot- com>wrote:
> Might be wrong about this, but in Chrome updates happen behind the scenes,
> right? I heard that was Google policy, to avoid pitfalls like M$ have with
> having to support different browser versions.
> If so, do you have to worry about that particular version? I heard that
> newest version is 17 (and it was supposed to have new JS engine).
> I heard / found nothing on Chrome being particular with tabber.js. Are you
> sure you're OK with your CFML code? It happens sometimes, that badly placed
> closure of cf tag will subtly break JS, and some browsers can live with
> that, some can't. Any errors in Chromebug console? Don't have Chrome here,
> so can't be more precise. In FB your sites seem clear.
> Tomasz Borek
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-