W3C home > Mailing lists > Public > www-style@w3.org > August 2013

Re: [cssom][css-page] Fixes for properly exposing @page in CSSOM

From: Simon Sapin <simon.sapin@exyr.org>
Date: Wed, 21 Aug 2013 11:55:13 +0100
Message-ID: <52149C91.20407@exyr.org>
To: www-style@w3.org
Le 21/08/2013 09:40, Simon Pieters a écrit :
> Hi,
> I have fixed bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=22500 and
> would like review of my proposed changes:
> https://dvcs.w3.org/hg/csswg/rev/048b4760e33e
> commit message:
> Expose the margin at-rules in @page as CSSMarginRule, uses type constant
> 9. Use a new interface for the declarations in @page and @top-left. Move
> the bulk of CSSStyleDeclaration to a new interface CSSDeclaration, and let
> CSSStyleDeclaration, CSSPageDeclaration and CSSMarginDeclaration inherit
>   from it.
> Constant 9 was unused according to wiki.csswg.org/spec/cssom-constants
> See http://dev.w3.org/csswg/css-page/ for more context and examples.

I disagree with CSSPageRule.style and CSSMarginRule.style having a 
different type from CSSStyleRule.style. Some properties "do not apply" 
to the page context or margin context just like the 'text-align' 
property does not apply to inline elements, that does not affect the OM.

@page and margin rules, like keyframe rules, contains "real" CSS 
properties and are much closer to style rules than eg. @font-face which 
contains descriptors that sometimes happen to have the same name as a 

The 'size' property is a bit odd in that it never applies to elements, 
but as currently defined it is a property and thus should appear in 

Simon Sapin
Received on Wednesday, 21 August 2013 10:55:44 UTC

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