W3C home > Mailing lists > Public > public-html@w3.org > May 2007

Re: Unscoped <style> found outside the <head>

From: Alan Dean <alan.dean@gmail.com>
Date: Sun, 27 May 2007 10:02:57 +0100
Message-ID: <6fb173f50705270202h20123910ke9dc8020bef822be@mail.gmail.com>
To: "David Hyatt" <hyatt@apple.com>
Cc: public-html@w3.org

Would this also work for 'river of news' style readers, for example
Google Reader, which do not reload the whole page? Without 'globally
unique scoping' I imagine that scope collisions would arise
frequently, possibly implying a considerable 'scope management tax'.

Alan

On 5/27/07, David Hyatt <hyatt@apple.com> wrote:
> <style scoped> would handle this use case.  A feed aggregator that
> did the stitching together of multiple feeds would want to add the
> scoped attribute if missing to any <style> elements from individual
> feed fragments anyway (to avoid style collisions between different
> feeds).
>
> The "stitching together" use case is where scoped style really
> shines.  I am proposing that <style scoped> would still be conformant
> if used outside the <head>, but that an unscoped <style> would not
> (because of its dangerous property of applying to the entire page
> content, which is virtually never what the author actually intended).
>
> dave
>
> On May 27, 2007, at 1:23 AM, Alan Dean wrote:
>
> > Dave,
> >
> > If I understand the nature of the markup constraint that you request,
> > would this not make html5 fragments much harder to work with, in the
> > context of RSS / Atom / etc feeds? The author does not control the
> > <head> element in that case, and so would be unable to apply any
> > inline styling to 'html5 conforming' fragments. Or am I missing
> > something?
> >
> > Regards,
> > Alan Dean
> > http://thoughtpad.net/alan-dean
>
>
Received on Sunday, 27 May 2007 09:03:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:44 UTC