- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Nov 2016 07:03:33 +0000
- To: public-css-archive@w3.org
I agree that the initial-letter's vertical position should not account for the floats. I think that's what the spec currently specifies, since it doesn't say otherwise, and doesn't define the initial letter as a float. (Though it could be moved down for floats if it actually doesn't *fit* next to them.) The horizontal position, on the other hand, does definitely need to account for floats, and does, since the initial letter is placed horizontally relative to the line, which is affected by floats... at least modulo issues like #689. Then there's the question of how the position of floats needs to account for the initial letter (the opposite direction of interaction from my previous two paragraphs), which is what the section currently covers. It could perhaps be retitled to make it clearer that it covers how floats move in response to initial letter, and not how initial letter moves in response to floats (which I believe is fully defined elsewhere). I believe floats whose placeholder/anchor is in a line after the first line of the block with initial-letter but one that does intersect the initial letter *do* need to be pushed down vertically past floats. Otherwise you'd have to find a way to address the circularity of placing a float in a way that would need to shorten a *prior* line (assuming a sensible fix for #689). I think the short text currently in the spec came out of a rather long working group discussion we had on this topic some time ago, although I'm not completely convinced it does so adequately (e.g., for opposite-side floats), but I haven't considered this closely. As the issue currently in the section notes, it's less clear whether we want that behavior for a float whose placeholder/anchor is in the *first* line of the block with initial-letter, since in that case it is entirely possible to displace the initial letter. (But is it desirable?) /cc @chenpighead -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/360#issuecomment-258761336 using your GitHub account
Received on Monday, 7 November 2016 07:03:45 UTC