- From: Roland Steiner <rolandsteiner@google.com>
- Date: Wed, 21 Sep 2011 08:44:34 +0000
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, public-webapps@w3.org
Received on Wednesday, 21 September 2011 08:45:29 UTC
A neat side effect of not rendering the host element (whether by "display: transparent", or implicitly) is that encapsulated styling of a component becomes trivial. I.e., one may want a component be isolated (i.e., not be able to access the main document by default, and vice versa), but still style the host element somehow. At the moment this requires 2 style-sheets: one to style the host element, and one to style the contents of the component. If the host element doesn't get a render box, only the latter remains, which is easy to encapsulate by putting a <style [scoped]> inside the component tree. - Roland On Wed, Sep 21, 2011 at 3:20 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 9/20/11 11:15 PM, Tab Atkins Jr. wrote: > >> I think this is properly a CSS issue. You want an element to not >> exist in the box tree, but to still have its children in the tree, >> which should be controllable with a display value, perhaps called >> 'transparent'. >> > > I believe that would be an acceptable solution to this use case, yes. If it > ever happens. > > -Boris > >
Received on Wednesday, 21 September 2011 08:45:29 UTC