W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: The Unwanted Effect of XBL Shadow DOM Elements on Layout

From: Charles Pritchard <chuck@jumis.com>
Date: Thu, 7 Apr 2011 12:34:46 -0700
Message-Id: <86F7F36B-EE73-419B-AC38-5D0472D8BE3E@jumis.com>
Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, www-style <www-style@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
When getting the canvas shadow Dom implemented in WebKit, we hit some related issues (though not the same issue).

I'd love to have that use case kept in mind when shadow dom is discussed. The canvas shadow Dom serves similar use cases to xbl, and it's likely to be a place where xbl via js is prototyped.


On Apr 7, 2011, at 11:45 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

> On Thu, Apr 7, 2011 at 11:13 AM, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote:
>> On 2011-04-07 16:52, Lachlan Hunt wrote:
>>> For this, one solution we came up with was a new value for 'display'
>>> that means to not generate a layout box for the element, but to still
>>> render the child content within as if the element itself wasn't there.
>>> display: transparent;
>> Apparently some people are confused by the use of the term transparent.
>>  Something like 'no-box' might be better.
> 'transparent' tracks perfectly with the HTML concept of a
> 'transparent' content model, which is why I liked it so much.
> ~TJ
Received on Thursday, 7 April 2011 19:35:18 UTC

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