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

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

From: Simon Pieters <simonp@opera.com>
Date: Wed, 21 Aug 2013 14:45:02 +0200
To: www-style@w3.org, "Simon Sapin" <simon.sapin@exyr.org>
Message-ID: <op.w1521cg9idj3kv@simons-macbook-pro.local>
On Wed, 21 Aug 2013 13:45:36 +0200, Simon Sapin <simon.sapin@exyr.org>  

> Le 21/08/2013 12:31, Simon Pieters a écrit :
>> My idea with this split was that we could reuse the machinery from
>> CSSStyleDeclaration for descriptors in e.g. @font-face. I still think  
>> this
>> can make sense for @font-face since descriptors and properties are  
>> similar
>> enough that they could be represented with the same interface in CSSOM.
> I agree this would make more sense than for @page, but I’m not convinced  
> this is a good idea. (I just don’t like CSSStyleDeclaration’s design.)
> How would it be better than the current definition of CSSFontFaceRule?
> http://www.w3.org/TR/2013/WD-css-fonts-3-20130711/#om-fontface

Consistency with the API developers are familiar with. If we have  
different ways to expose things that are similar, developers have to look  
up or trail and error every time.

Simon Pieters
Opera Software
Received on Wednesday, 21 August 2013 12:39:35 UTC

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