Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Google-chrome-frame
Home
+ new post
About this group
Join this group
Message from discussion Compatibility mode expressed in response header
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alex Russell  
View profile  
 More options Sep 22 2009, 3:45 pm
From: Alex Russell <slightly...@google.com>
Date: Tue, 22 Sep 2009 12:45:14 -0700
Local: Tues, Sep 22 2009 3:45 pm
Subject: Re: [google-chrome-frame:1] Compatibility mode expressed in response header
Print | View thread | Show original | Report this message | Find messages by this author
Hey Niall!

On Tue, Sep 22, 2009 at 12:19 PM, Niall Kennedy <ni...@niallkennedy.com> wrote:

> The X-UA-Compatible flag introduced in IE8 supports declaration in the
> page via a meta element or as a field in the response header.
> http://msdn.microsoft.com/en-us/library/cc817574.aspx

Correct. Right now, we aren't supporting the HTTP header (although we
do support a separate MIME type, application/chromeframe) in part
because reading the network traffic isn't something we'd like to do.
We're actively looking at other ways of toggling the renderer, and the
<meta> tag solution is the most robust across all the various
solutions.

Depending on how it all goes, we might support the header, but there
aren't plans to right now.

> Chrome Frame currently supports only the meta method, based on
> available docs.
> http://code.google.com/chrome/chromeframe/developers_guide.html#Makin...

> Any plan to support site owners specifying support via HTTP header?

> Providing a multiple key-value example in the docs should help
> implementors (e.g. ie=8;chrome=1).

That's true.

> How will Chrome frames be versioned? If Google Chrome for Windows is
> currently at a major version of 3, and Chromium at 4, what is the
> meaning of your value of "1" (other than boolean?).

It's boolean for the time being. We won't be installing or allowing
multiple versions of Chrome Frame, so boolean is appropriate. Nearly
all users will eventually be on the Stable Channel Chrome Frame, so
setting a toggle for them wouldn't really help.

The good news here is that Chrome Frame auto-updates on the same cycle
as Chrome. Across the deployed base, there will be one version, and
it'll be continuously improving.

Regards


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google