Ah, sorry for the confusion - my use of "default" was indeed sloppy. I'm saying that if the server is explicitly specifying the charset either via a header or via BOMs, it seems bad to ignore it since there's no other way to override the charset.<div>
<br></div><div>I understand your point, though - since workers don't inherit the document encoding from their parent, they may indeed decode a given resource differently if the server isn't specifying a charset in some way.<br>
<div><div><br></div><div>-atw<br><div><br><div class="gmail_quote">On Mon, Sep 28, 2009 at 4:47 AM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@opera.com">annevk@opera.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 25 Sep 2009 19:34:18 +0200, Drew Wilson <<a href="mailto:atwilson@google.com" target="_blank">atwilson@google.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Again, apologies if I'm misunderstanding the suggestion.<br>
</blockquote>
<br></div>
I thought that by "default encoding" you meant the encoding that would be used if other means of getting the encoding failed. If there is only one encoding it is not exactly the "default", since it cannot be changed.<div>
<div></div><div class="h5"><br>
<br>
<br>
-- <br>
Anne van Kesteren<br>
<a href="http://annevankesteren.nl/" target="_blank">http://annevankesteren.nl/</a><br>
</div></div></blockquote></div><br></div></div></div></div>