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

Re: Parsing of HTML fragments

From: Preston L. Bannister <preston@bannister.us>
Date: Tue, 24 Apr 2007 16:44:37 -0700
Message-ID: <7e91ba7e0704241644t8735e7bp44a3f0e6899beb85@mail.gmail.com>
To: "Ian Hickson" <ian@hixie.ch>
Cc: "Dão Gottwald" <dao@design-noir.de>, "Edward O'Connor" <hober0@gmail.com>, public-html@w3.org, foolistbar@googlemail.com
On 4/24/07, Ian Hickson <ian@hixie.ch> wrote:
>
> On Tue, 24 Apr 2007, Dão Gottwald wrote:
> > > If this WG adopts the WHATWG draft, I imagine this would be handled by
> > > the innerHTML parsing mode.
> >
> > Um, not necessarily. A feed consumer doesn't have to use innerHTML to
> > insert fragments into a given document. In fact, HTML fragments can be
> > delivered as XML nodes instead of CDATA.
>
> The "innerHTML parsing mode" isn't restricted to innerHTML; it's just a
> way to parse fragments with a particular context. You can use the
> algorithm described for innerHTML in the spec for other purposes, such as
> this one.
>


Seems like HTML fragments, such as embedded in Atom feeds, should contain
structure, rather than any specific presentation.  Plugging the fragment
into innerHTML should yield the same structure independent of the version or
mode of the parent document.  Presentation could be different, but
presentation should be controlled by the parent document.

A lot of this is going to depend on the application.  Guess the question is,
to pick a specific case - should the Atom spec disallow too-new HTML tags?
Should Atom disallow presentation-related tags (like <font>) that are
unlikely to play well in the parent document?
Received on Tuesday, 24 April 2007 23:44:53 UTC

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