W3C home > Mailing lists > Public > www-style@w3.org > January 2014

[css-break] page break aliases vs getComputedStyle

From: Peter Moulder <pjrm@mail.internode.on.net>
Date: Wed, 15 Jan 2014 15:01:58 +1100
To: www-style@w3.org
Message-ID: <20140115040158.GB10093@mail.internode.on.net>
I'm not at all familiar with scripting things, so forgive me if the answer
should actually be obvious to most people, or if I cite an out-of-date spec.

Section 3.4 ‘Page Break Aliases: ...’ says that UAs should "[treat]
page-break-* as shorthands", while 
http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration-getPropertyCSSValue
says that getPropertyCSSValue should return null for shorthands.

Do I correctly infer that UAs that conform to css-break must return null
for getComputedStyle(...).getPropertyCSSValue("pageBreakBefore")
(even when there is an explicit page-break-before declaration), while
other (CSS21-like) UAs must return non-null ?

If so, I suggest drawing attention to this (given that this paragraph says that
the intent is to preserve compatibility with CSS Level 2).  

Otherwise, I suggest stating what the rules for what it should return in this
case (e.g. with a declaration like "break-before: page" or "break-before:
column" or "page-break-before: always").

(Again, sorry if the above comment arises only because of my unfamiliarity with
this area.)

pjrm.
Received on Wednesday, 15 January 2014 15:04:42 UTC

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