Received: by 10.224.117.143 with SMTP id r15mr13455559qaq.1.1350567655286; Thu, 18 Oct 2012 06:40:55 -0700 (PDT) X-BeenThere: google-chrome-frame@googlegroups.com Received: by 10.229.178.132 with SMTP id bm4ls78306qcb.6.gmail; Thu, 18 Oct 2012 06:40:54 -0700 (PDT) Received: by 10.224.52.200 with SMTP id j8mr977258qag.5.1350567654121; Thu, 18 Oct 2012 06:40:54 -0700 (PDT) Received: by 10.224.67.196 with SMTP id s4msqai; Thu, 18 Oct 2012 06:38:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.175.5 with SMTP id bw5mr3554018vdc.16.1350567508479; Thu, 18 Oct 2012 06:38:28 -0700 (PDT) Authentication-Results: ls.google.com; spf=pass (google.com: domain of matthew.sta...@ineos.com designates internal as permitted sender) smtp.mail=matthew.sta...@ineos.com; dkim=pass header...@ineos.com Received: by b19g2000vbt.googlegroups.com with HTTP; Thu, 18 Oct 2012 06:38:28 -0700 (PDT) Date: Thu, 18 Oct 2012 06:38:28 -0700 (PDT) In-Reply-To: References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4,gzip(gfe) Message-ID: <0571ac10-4542-40a6-b0ea-12fac1deab52@b19g2000vbt.googlegroups.com> Subject: Re: CF updates, compatibility with Google Apps From: Matthew Stamps To: Google-chrome-frame Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am having the same issue also on Google Drive. I too am testing CF with IE8 and this is an unexpected bump in the road! On Oct 9, 2:06=A0pm, ValleyJim wrote: > Lately our Google Apps users have been getting warnings about Google's en= d > of support for IE8. =A0I'm evaluating CF as a workaround, and I hope some= one > here can help. > > In the last week or two I first started testing CF with IE8, and as a tes= t > I used group policy to force CF as the default HTML renderer for all > sites. =A0I know that it was working because IE passed Acid3 with 100%. = =A0When > I went to Google Drive, however, it warned me that I was using an obsolet= e > web browser. =A0So I started to wonder if Drive would acually be supporti= ng > IE8 with CF. =A0I resumed my testing today, but now I'm getting a differe= nt > warning from Drive. =A0It says, "You are using an out of date version of > Google Chrome. =A0Some features may not work correctly. =A0Upgrade to the > latest version." =A0I got that message with the regular CF channel, which= I > think was version 21.x.x.x. =A0Now I'm on the beta channel, I think, with= CF > version 23.0.1271.22, and am still getting the same out-of-date warning. > Questions: > > =A0 =A0- The errors I got - first saying that IE8+CF would soon be unsupp= orted, > =A0 =A0now saying that Chrome is out of date - are these merely browser s= niffing > =A0 =A0problems or is there something bigger going on? > =A0 =A0- Do we know officially whether Google Apps will fully support IE8= +CF? > =A0 =A0- Unless I'm mistaken, Chrome is at version 22 while CF is at > =A0 =A021. =A0Should CF updates occur at the same time as Chrome, or is a= lag > =A0 =A0expected? > =A0 =A0- Is it possible to allow CF to activate only on those sites that = I > =A0 =A0specify, ignoring sites using the chrome=3D1 metatag? =A0This woul= d be > =A0 =A0important from a security standpoint, especially if CF updates are= not > =A0 =A0going to be released promptly with Chrome. > > Thank you for your help.