W3C home > Mailing lists > Public > public-html@w3.org > February 2009

Re: Foster-parenting and taint

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 25 Feb 2009 16:25:28 +0200
Message-Id: <FC0BC101-EDE5-43F4-BBED-67935154E645@iki.fi>
To: HTMLWG WG <public-html@w3.org>
On Feb 25, 2009, at 15:28, Henri Sivonen wrote:

> Opera and IE prior to IE8 mode don't foster parent in the DOM. The  
> visual effect is similar to foster parenting, but content that was  
> before the <table> tag in source and content that was after are  
> rendered on different lines unlike in Gecko and WebKit.


To elaborate:

If one accepts the level of rendering differences that exist between  
Gecko/spec and IE7/Opera or WebKit and IE7/Opera as a sufficient level  
compat to be able to ship a browser, the difference in handling  
leading space characters (i.e. <table>  x</table>) between Gecko/spec  
and WebKit shouldn't matter either way. I'd even argue that the WebKit  
behavior is closer to IE7/Opera, because it doesn't join words  
accidentally.

It seems to me that tainting works better than the late flushing  
approach only in a case where comments surround a space that should  
actually separate words:
<table>foo<!-- --> <!-- -->bar</table>

This doesn't look like a compelling justification for keeping the  
tainting machinery around.

Furthermore, adopting the WebKit text foster parenting behavior would  
require violating the incremental text node rendering principle only  
if the insertion mode is "in table", "in table body" or "in row". (I'm  
currently trying to see if I can get away with violating the principle  
in all of the tree builder anyway...)

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Wednesday, 25 February 2009 14:26:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:01 UTC