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

Re: handling fallback content for still images

From: James Graham <jg307@cam.ac.uk>
Date: Mon, 09 Jul 2007 10:41:36 +0100
Message-ID: <469202D0.9000601@cam.ac.uk>
To: Robert Burns <rob@robburns.com>
Cc: public-html@w3.org

Robert Burns wrote:
> The point Henri, is you took a thread about something else and turned it 
> into a discussion about the parser. It wasn't about the parser until you 
> arrived. The confusion was introduced when you made it about the parser. 
> It was about HTML5 UAs (bigger than the parser).

Sorry, I'm really confused.

It would be really helpful if you could summarize the issues that you 
are trying to address in this thread; I really seem to be lost amongst 
the various discussions and subthreads.

It would be really useful if, any time you want to talk about the 
parsing-behavior of current UAs, you could post the source of some 
example input and DOM produced from that input. The Live DOM Viewer 
should make this easy for the non-XML case. It would also be helpful if 
you could compare this behavior with that in the current spec; the 
html5lib parsetree viewer provides a simple[1] way to do this.

Sorry to anyone who is following this thread (or anyone who simply 
doesn't care about this topic) for the extra email. I hope at least 
someone else will find the clarification helpful.

Thanks

[1] But, of course, possibly buggy!

-- 
"Mixed up signals
Bullet train
People snuffed out in the brutal rain"
--Conner Oberst
Received on Monday, 9 July 2007 09:41:45 UTC

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