W3C home > Mailing lists > Public > www-style@w3.org > July 2015

RE: [css-break] Name of 'any' value confusing

From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Date: Wed, 15 Jul 2015 18:52:58 +0000
To: Brady Duga <duga@ljug.com>, W3C style mailing list <www-style@w3.org>
Message-ID: <BY2PR03MB192A3C64A1073D1FA0A5AFB9B9A0@BY2PR03MB192.namprd03.prod.outlook.com>
> -----Original Message-----
> From: Brady Duga [mailto:duga@ljug.com]
> Sent: Friday, March 20, 2015 5:14 PM
> 
> I know naming is everyones favorite topic so... The 'any' break type confused
> me, since it is really a type of always. Maybe make it always-any? Or always-
> deepest? I suppose 'always' might want to be always-all.

The values of the break properties are supposed to reflect the behavior from the point of view of a box being inside of some nested fragmentation contexts. In that respect the intend of 'any' was to allow breaking (or avoidance etc.) on any of these fragmentation contexts regardless of what they are (column, page, region etc.) so long as they are forcing breaks. 

At this point we're not really married to the 'any' keyword but when working through the spec it was the best option. Perhaps if the 'always' keyword was 'all' then 'any' will make a lot more sense. We decided to adopt 'always' due to CSS 2.1 page breaking compat.

Here're some other names we could try  
'nearest', 'closest', 'first'
'any-available', 'any-enforcing'

Bottom line is that we're open to suggestions as long as they're better than 'any' in terms of describing the fact that break must occur regardless of the fragmentainer type. Also the name should be expressed from the point of view of the box looking "up" in the fragmentation contexts.

Thanks,
Rossen
Received on Wednesday, 15 July 2015 18:53:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC