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

RE: @page margin boxes and text-decoration

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Sun, 18 Jan 2009 23:00:54 -0800
To: Michael Day <mikeday@yeslogic.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
CC: "www-style@w3.org" <www-style@w3.org>, "Grant, Melinda" <melinda.grant@hp.com>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D0206B5678CA1D@NA-EXMSG-C103.redmond.corp.microsoft.com>

Your inheritance concern is not about @page, it is about text-decoration, right? That is true, inheritance rules for that are unique ("see prose" is the best we can do for formal definition)... otherwise paged media doesn't make inheritance more difficult - or does it?

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Michael Day
Sent: Sunday, January 18, 2009 10:51 PM
To: Bjoern Hoehrmann
Cc: www-style@w3.org; Grant, Melinda
Subject: Re: @page margin boxes and text-decoration

Hi Bjoern,

> I am unsure where the confusion arises from, according to the draft the
> text-decoration declaration sets the initial value of the property in
> the margin boxes, so, as I understand that, this would essentially be
> the same as

You're right, I missed that, and Prince doesn't implement it.

To be honest, I'm not sure I like the idea of having yet another
inheritance category, it seems simpler to say that properties inherit
from @page to margin boxes in exactly the same way that they inherit
from elements to child elements.

The most common use case is to specify the same font and color for
multiple margin boxes, and inheritance already takes care of this.

Best regards,


Print XML with Prince!
Received on Monday, 19 January 2009 07:01:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC