- From: Glenn Adams <glenn@skynav.com>
- Date: Wed, 24 Oct 2012 09:06:23 +0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style@w3.org
- Message-ID: <CACQ=j+crZzNSAWcbtLbRzY1DJ7mCzkG+CfYR3qSeWYMvvDASZQ@mail.gmail.com>
On Tue, Oct 23, 2012 at 9:36 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 10/23/12 4:06 AM, Glenn Adams wrote: > >> If the resource containing the stylesheet and the resource containing >> the referencing document are both in the same domain (foo.com >> <http://foo.com>), then it might be reasonable. However, if cross >> >> domain, then it would be inadvisable. >> > > That's a possible refinement on what's currently specified and > implemented, yes. > > That said, it's not clear to me how much we really want to rock the compat > boat here, unless there are security considerations. > > > Also, it would be useful to point out the use >> of the charset MIME type parameter on the @type attribute from the >> linking element, which seems like it would be covered by rule (3), but >> is not otherwise mentioned. >> > > In Gecko, it's not considered as a source of encoding information. I > don't know what other UAs do, offhand. Just for clarification, do you mean that the encoding of the referencing resource is not used or the charset param on @type is not used or both are not used in FF?
Received on Wednesday, 24 October 2012 01:07:10 UTC