- From: Kang-Hao (Kenny) Lu <kanghaol@opera.com>
- Date: Mon, 11 Nov 2013 12:35:32 +0800
- To: WWW Style <www-style@w3.org>
I think the keyword value 'each-line' is misleading but I agree 'after-break' as proposed by HÃ¥kon[1] is not converying the right intent either. What about 'each-paragraph'? Fundamentally, I am not sure what use case this value is trying to solve, and why isn't it solved by 'padding'. I treat it as a fix for this case <div> <p>Some pargraph...</p> This is a new paragraph but it don't get 'text-indent' without this new value. </div> , which is somewhat mysterious because before I read the spec and tested it, I supposed the anoymous block would inherit 'text-indent' from <div> per CSS2.1 but it does not... (The rest is probably editorial but let's give the spec some theoritcal rigor :) # The indent is treated as a margin applied to the start edge of # the line box. This is somewhat ambiguous because it's not clear if the width of the line box is calculated as either * A block-level box, where margin decreases the width. * A inine box, where the width is a constant. We obviously want the first and not "shifted line box", and this should be clarified. I also think it would nice to specify that the 'width' of a line box is determined by: * First, lay out floats and do the line box shortening. * Second, apply 'text-indent' for further shortening. * Thrid, push line box down and jump to first if no content. Or otherwise, any ordering of the above seems to be allowed by the current specs. I haven't observed any incompability on this but I haven't tested IE and Presto.... [1] http://lists.w3.org/Archives/Public/www-style/2011May/0721 Cheers, Kenny -- Web Specialist, Opera Sphinx Game Force, Oupeng Browser, Beijing Try Oupeng: http://www.oupeng.com/
Received on Monday, 11 November 2013 06:08:28 UTC