Re: [css3-text] Re: Orphan control in CSS

I have an article pending review for inclusion at A List Apart (at the
request of Jeffrey Zeldman) which is entirely focused on the
deficiencies of CSS Type. Major issues are:

1) The poor way the font-stack and dependent attributes work
2) An utter lack of baseline control in anything other than the current element

These are the two huge problems where CSS is very defcient. Would the
www-style group be interested in reading the article prior to
(possible) publication?



On 6 January 2012 08:43, Koji Ishii <kojiishi@gluesoft.co.jp> wrote:
>> From: L. David Baron [mailto:dbaron@dbaron.org]
>>
>> I don't like it.  I haven't heard of control to prevent a single (or other small number) of
>> words on the last line as being a feature people use without also having a line breaking
>> algorithm that would take the words from somewhere other than the next-to-last line, i.e.,
>> a line breaking algorithm that does whole-paragraph (or at least bunch-of-lines-at-a-time)
>> optimization.  I tend to think that without whole-paragraph line break optimization, it's just
>> going to make things look funny and authors aren't going to want to use it (perhaps with
>> exceptions for very limited cases, like headings that will appear on either one or two lines).
>
> It sounds like you assume that browsers do not do paragraph-level-optimizations. Without knowing much of the history, is it too wild to start thinking about having paragraph-level-optimizations in browsers?
>
> Documents on the web is getting much longer, and people use browsers to read books these days. I think better readability and typography helps browsers. If performance is still a concern, it could switch typography engine by property, like InDesign does.
>
>
> Regards,
> Koji

Received on Friday, 6 January 2012 10:11:04 UTC