- From: David Hyatt <hyatt@apple.com>
- Date: Thu, 20 May 2010 14:20:59 -0500
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: www-style list <www-style@w3.org>
On May 20, 2010, at 2:09 PM, Boris Zbarsky wrote: > On 5/20/10 2:41 PM, David Hyatt wrote: >> The above model would be very easy to implement in WebKit. > > Would it, though? The existing block-inside-inline implementation in Gecko is pretty complex (especially in order to handle dynamic changes efficiently). WebKit's approach to the dynamic change issue seems to be to just mishandle them in various cases [1]. There are also issues with generated content in WebKit [2]. And issues with containing blocks [3]. So if the "easy to implement" claim is based on analogy with block-in-inline, I don't buy it, sorry. My experience is that getting block-inside-inline right is a huge pain. > I don't disagree. What I meant by "easy" is that it could piggyback on a lot of the existing block-inside-inline code in WebKit rather than forcing us to write a huge pile of brand new code. Block-inside-inline obviously introduces a lot of complexity, and I think column-span introduces a similar level of complexity. As I said in my opening message, I'd be content with just dropping it. I'm suggesting an implementation model if it doesn't get dropped though. dave
Received on Thursday, 20 May 2010 19:28:40 UTC