- From: David Carlisle <davidc@n...>
- To: Kurt Cagle <kurt.cagle@g...>
- Date: Sat, 18 Dec 2010 15:54:18 +0000
On 18/12/2010 14:22, Kurt Cagle wrote:
> So you end up with problematic elements such as <br/>, which in XML is
> interpreted as an empty element named "br" with no children, being
> interpreted in HTML5 as <br></br> as an element with an associated text
> node, albeit one with a string-length of 0?
no html5 parses <br/> exactly as if the input had been <br>.
In either case it parses to make a void element with no child nodes.
David
- References:
- Never mind the browser, let's do MicroXML
- From: Uche Ogbuji <uche@o...>
- Re: Never mind the browser, let's do MicroXML
- From: Michael Kay <mike@s...>
- Re: Never mind the browser, let's do MicroXML
- From: Uche Ogbuji <uche@o...>
- Re: Never mind the browser, let's do MicroXML
- From: Rob Koberg <rob@k...>
- Re: Never mind the browser, let's do MicroXML
- From: Kurt Cagle <kurt.cagle@g...>
- Re: Never mind the browser, let's do MicroXML
- From: David Carlisle <davidc@n...>
- Re: Never mind the browser, let's do MicroXML
- From: Kurt Cagle <kurt.cagle@g...>
- Re: Never mind the browser, let's do MicroXML
- From: David Carlisle <davidc@n...>
- Re: Never mind the browser, let's do MicroXML
- From: Kurt Cagle <kurt.cagle@g...>
- Re: Never mind the browser, let's do MicroXML
- From: David Carlisle <davidc@n...>
- Re: Never mind the browser, let's do MicroXML
- From: Kurt Cagle <kurt.cagle@g...>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
Cart
