W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2008

[Bug 5753] parsing issues with legacy UAs

From: <bugzilla@wiggum.w3.org>
Date: Sat, 14 Jun 2008 12:31:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1K7Uul-0005Sq-IE@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5753





--- Comment #5 from Lachlan Hunt <lachlan.hunt@lachy.id.au>  2008-06-14 12:31:27 ---
(In reply to comment #4)
> So regardless of legacy UAs and just focussing on HTML5 UAs: 
>   How would a UA serialize the DOM tree I gave in the above comment #2 example
> in a way that could be parsed into a HTML5 text/html processor without loss of
> data?

That is one of the well known differences between HTML and XHTML, and we are
very much constrained by our backwards compatibility design principle.  It is
not possible to represent all possible documents in each of the three
representations: HTML, XHTML and DOM. This is even mentioned in the spec.

http://www.whatwg.org/specs/web-apps/current-work/#html-vs

Unfortunately, we just have to accept that this is not something we have the
luxury of being able to fix in all cases.

There is also a section discussing the content model restrictions that apply to
the HTML syntax.

http://www.whatwg.org/specs/web-apps/current-work/#element-restrictions

Note that although the specific example of UL inside P that you gave isn't
mentioned in that section, it probably should be and that appears to be a bug
in the spec.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 14 June 2008 12:32:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 14 June 2008 12:32:01 GMT