W3C home > Mailing lists > Public > www-style@w3.org > June 2012

Re: [css3-cascade] inheritance and ::backdrop

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 25 Jun 2012 16:18:48 -0700
Message-ID: <4FE8F1D8.2070903@inkedblade.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Anne van Kesteren <annevk@annevk.nl>, www-style@w3.org
On 06/25/2012 03:34 PM, Tab Atkins Jr. wrote:
> On Mon, Jun 25, 2012 at 3:11 PM, fantasai<fantasai.lists@inkedblade.net>  wrote:
>> On 06/25/2012 02:19 PM, Tab Atkins Jr. wrote:
>>> On Thu, Jun 21, 2012 at 3:14 PM, fantasai<fantasai.lists@inkedblade.net>
>>>   wrote:
>>>> Also, to be precise, you're not actually clear about what happens to e.g.
>>>> 'color', which is an inheritable property. If it doesn't inherit from
>>>> anything, what is it's value? This is not defined, because currently in
>>>> CSS every element has a parent except the root, and there is a special
>>>> exception to inheritance specifically for the root element.
>>> ...which we should fix, so that we can have a sensical story about
>>> disconnected fragments.  It just requires wordsmithing, since the
>>> answer is obvious - replace all the "is root" checks with "doesn't
>>> have a parent".
>> What do you mean by disconnected fragments?
> For example, the issue we have with SVG fragments created by script
> and not inserted into a document, but referenced by element().

Ah, fair point. Then let's deal with this in CSS3 Cascade.

(I'm still not sure it's the right thing to do for ::backdrop, but we
should fix it nonetheless.)

Received on Monday, 25 June 2012 23:19:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:00 UTC