Howdy,
As you may have heard, Google Chrome Frame is a plugin that helps web
authors target modern standards and renderer features. The current
mechanism for this switch is a value for an http-equiv meta tag, the
same mechanism which IE 8 introduced for helping authors ensure
renderer-level
On Wed, Oct 7, 2009 at 2:01 PM, Alex Russell slightly...@chromium.org wrote:
we'd like to request
that an exception be made to the registered via RFC rule for
http-equiv headers which are prefixed with X-, or, alternately, that
the spec simply declare that unlisted keys and values will not be
On Wed, Oct 7, 2009 at 11:20 AM, Aryeh Gregor simetrical+...@gmail.com wrote:
On Wed, Oct 7, 2009 at 2:01 PM, Alex Russell slightly...@chromium.org wrote:
we'd like to request
that an exception be made to the registered via RFC rule for
http-equiv headers which are prefixed with X-, or,
On Tue, Oct 6, 2009 at 6:33 PM, David Workman workm...@gmail.com wrote:
I don't know about others, but that just looks ugly to me (the repetition of
'cite' looks unnecessary). I know elegance isn't crucial, but given the
choice between cite for= and cite cite= I'd go for the former.
As a
On Wed, Oct 7, 2009 at 6:51 PM, David Workman workm...@gmail.com wrote:
I agree that href would be better than src due to the reasons you gave.
However, rather than adding a new attribute of alias, could cite instead
be given a name attribute that works similar to radio button names in forms
On 10/7/09 7:12 PM, Kartikaya Gupta wrote:
If a document is served as text/html, but contains an XML prolog with an
encoding attribute, it seems that all Firefox, Opera, and Chrome all pick up
the encoding from the prolog and use it when parsing the rest of the document.
(IE6 does not). The
On Wed, 07 Oct 2009 19:34:18 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/7/09 7:12 PM, Kartikaya Gupta wrote:
If a document is served as text/html, but contains an XML prolog with an
encoding attribute, it seems that all Firefox, Opera, and Chrome all pick
up the encoding from the
On Wednesday 2009-10-07 23:51 +, Kartikaya Gupta wrote:
On Wed, 07 Oct 2009 19:34:18 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/7/09 7:12 PM, Kartikaya Gupta wrote:
If a document is served as text/html, but contains an XML prolog with an
encoding attribute, it seems that all
On Wed, 07 Oct 2009 20:04 -0400 L. David Baron wrote:
Maybe you've configured UTF-8 as the fallback encoding? It's a preference
(and its default value varies between localizations).
Tools - Options - Content - Fonts Colors - Character Encoding
- Default Character Encoding. (For other
On 10/7/09 7:51 PM, Kartikaya Gupta wrote:
I tried it again in Chrome and if I paste the above in the address bar I get
US-ASCII. But if I save it to a file and then load it I get UTF-8. I checked
the headers being sent from Apache and they don't include any sneaky encoding
hints, just
On Wed, 07 Oct 2009 20:23:35 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/7/09 7:51 PM, Kartikaya Gupta wrote:
I tried it again in Chrome and if I paste the above in the address bar I
get US-ASCII. But if I save it to a file and then load it I get UTF-8. I
checked the headers being
On 10/7/09 9:29 PM, Kartikaya Gupta wrote:
Using document.inputEncoding:
http://stakface.com/pub/mango/fakexml.html
http://stakface.com/pub/mango/fakexml_iso.html
Using a degree symbol in UTF-8:
http://stakface.com/pub/mango/fakexml2.html
http://stakface.com/pub/mango/fakexml2_iso.html
All of
On Sun, Sep 20, 2009 at 2:26 PM, Juriy Zaytsev kangax@gmail.com wrote:
On Sep 20, 2009, at 5:20 PM, Joseph Pecoraro wrote:
On Sep 20, 2009, at 4: 24PM, Juriy Zaytsev wrote:
Speaking of `document.head`, I think Mootools does exactly that.
Good thinking. I took a look at some
On Wed, 07 Oct 2009 21:35:00 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/7/09 9:29 PM, Kartikaya Gupta wrote:
Using document.inputEncoding:
http://stakface.com/pub/mango/fakexml.html
http://stakface.com/pub/mango/fakexml_iso.html
Using a degree symbol in UTF-8:
fakexml.html and fakexml2.html both work as UTF-8 for me in Safari 4 and
Firefox 3 on Mac.fakexml_iso.html shows up as UTF-8 in Safari 4, but
ISO-8859-1 in Firefox.
fakexml2_iso.html has a broken degree in both Safari and Firefox.
So for me, you can get the XML prolog to override the encoding,
On 10/7/09 9:52 PM, Kartikaya Gupta wrote:
Anything else that might be affecting this?
In general, yes. Charset info can come from the HTTP cache, from user
bookmarks, etc, etc.
In this case, though, it's totally my fault: I just forgot that I had
the HTML5 parser turned on locally.
In this case, though, it's totally my fault: I just forgot that I had
the HTML5 parser turned on locally. Turning that off, I do get UTF-8,
because of
http://hg.mozilla.org/mozilla-central/file/603759afc77a/parser/htmlparser/src/nsParser.cpp#l2553
and following. That code is just
On 10/8/09 12:26 AM, Kartikaya Gupta wrote:
So then is this behavior getting axed or specced?
Good question. It might just be that it's needed for compat with sites
sending XHTML as text/html :(
-Boris
18 matches
Mail list logo
