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: Thu, 13 Dec 2012 10:56:38 +1100
Cc: www-style mailing list <www-style@w3.org>
Message-id: <90563EB4-57EA-45C9-9F8E-ED93701D65BD@apple.com>
To: www-style@gtalbot.org

On 13/12/2012, at 10:21 AM, Gérard Talbot <www-style@gtalbot.org> wrote:

> I do not understand why Webkit can not implement orphans and widows
> according to CSS2.1 specification.
> I do not understand why you say that it would break existing content.

Because these properties have implied behaviour on content, even when
they were never specified by the author. Now, after years, our implementation
turns them on and things change. I doubt any author will understand
why. Whether or not it is a positive change is important, but not really
our decision to make.

> If webkit does not implement orphans and widows with a default, initial
> value of 2, then it will break web-standards-compliant content,
> web-interoperability and cross-browser-compatibility. Now and later.

That's why I sent the email - so we could discuss the issue.

> Regarding "to not break existing content", I am convinced that a very wide
> majority of existing web content do not use, do not declare 'widows' and
> 'orphans'.

Yes, that's exactly my point! If they did use and declare these properties,
we obviously wouldn't be breaking them. That's the way CSS works.

Received on Wednesday, 12 December 2012 23:57:16 UTC

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