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

Re: edge issues with DOM, text/html, and xml serializations [was Re: handling fallback content for still images]

From: Andrew Sidwell <takkaria@gmail.com>
Date: Mon, 09 Jul 2007 17:12:31 +0100
Message-ID: <46925E6F.50707@gmail.com>
To: Robert Burns <rob@robburns.com>
CC: James Graham <jg307@cam.ac.uk>, public-html@w3.org

Robert Burns wrote:
> On Jul 9, 2007, at 9:34 AM, James Graham wrote:
>> Robert Burns wrote:
>>> Despite some confusion on these issues, there isn't a single
>>> right way to do these things and the sooner we can acknowledge
>>> that the easier our task will be.
>>
>> If you're talking about XML parsing there really is only one way to do
>> it; the DOM you get is determined by the XML spec. Any browser that
>> does something different has a bug.
> 
> I've been working with primarily XML for nearly a year now (CSS and DOM
> and translation). And I can tell you it's not as unambiguous as you
> might think. There's definitely ambiguity and there's room to clear up
> ambiguity. The XML spec is most clear on well-formedness. After that,
> there's wiggle room.

Instead of just stating "there's wiggle room", please could you give
examples of where such room exists?  It's very hard to understand any of
the issues involved based on such vague statements.

Andrew Sidwell
Received on Monday, 9 July 2007 16:22:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT