W3C home > Mailing lists > Public > www-style@w3.org > December 2012

Re: Initial values for widows and orphans

From: Dean Jackson <dino@apple.com>
Date: Tue, 11 Dec 2012 10:53:27 +1100
Message-id: <AB809FB0-E3B3-4851-A9CB-DB57445178FD@apple.com>
To: www-style@w3.org

On 11/12/2012, at 8:56 AM, fantasai <fantasai.lists@inkedblade.net> wrote:

> On 12/10/2012 01:34 PM, Dean Jackson wrote:
>> I just added support for 'widows' and 'orphans' to WebKit [1].
>> Unfortunately, in order to not break existing content, I couldn't use the specified initial values of 2.
>> Instead I had to go against the spec and accept a value of 'auto'
>> and have that be the initial value. In WebKit, this means do nothing
>> (do not try to avoid widows or orphans).
> widows and orphans only accept integers. If you want "do nothing", why
> aren't you using 1 as the initial value?

OK. I'll change it to 1.

>> What was the reasoning behind having such initial values? [2] [3]
> Probably because in general, it results in better pagination of text
> content. It's been that way since CSS2.0.
>  http://www.w3.org/TR/2008/REC-CSS2-20080411/page.html#break-inside

Sure, I get that. But my question was more about adding a property that
"breaks" existing content. That's the position we're in. We didn't
support the properties before now, and we can't use the initial value
without introducing regressions.

It's not a big deal, just a minor annoyance. Technically we won't
comply with the specification.

Received on Monday, 10 December 2012 23:53:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:24 UTC