For reference, I wrote down all different variants of rendering and styling
of the host element/shadow root I could think of at:
http://wiki.whatwg.org/wiki/Component_Model_Discussion:_Rendering
Cheers,
- Roland
On Wed, Sep 28, 2011 at 5:14 AM, Julien Richard-Foy
jul...@richard-foy.frwrote:
On 9/27/2011 10:26 PM, Roland Steiner wrote:
On Fri, Sep 23, 2011 at 1:58 AM, Charles Pritchard ch...@jumis.com
mailto:ch...@jumis.com wrote:
[...]
We have an opportunity now to document the sub-elements of single
form controls.
That is certainly a very valid goal. For
Tab: How well is display: transparent received, eg on www-style?
I have a feeling this question—whether to render the host or not—depends on
whether you are using shadow DOM with components, or with existing elements.
When you want to use shadow DOM with components, the current solution seems
OK
Hi,
If I understand correctly you are planing to allow shadow dom to be styled by
users stylesheets.
I’m not sure it will be a good idea since it would break encapsulation.
Regards,
Julien
On Fri, Sep 23, 2011 at 1:58 AM, Charles Pritchard ch...@jumis.com wrote:
[...]
We have an opportunity now to document the sub-elements of single form
controls.
That is certainly a very valid goal. For example, it would really be great
if an author could create his/her own video element and
I've snipped the transcript to parts relevant to my top-posted discussion.
We already have web components; there are two shimmering examples on the
net right now.
1.
First, there's Canvas. Canvas has a subtree, and at some point earlier
on, it was referred to as the Canvas shadow dom.
In
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
Context: Last week some Bay Area/visiting Bay Area browser hackers met
to discuss the component model
http://wiki.whatwg.org/wiki/Component_Model This is my unedited
transcript. I am not much of a stenographer so no doubt there are
gaps.
Cast of characters:
boris--Boris Zbarsky
dg--Dimitri
A comment on use cases that was brought up over here.
There's a use case that is not addressed by XBL1 and impossible to quite
address in a JS library that goes as follows. Say you have some data in
a table. Semantically it's a data table. But you may want to present
it as a graphic (SVG
On Tue, Sep 20, 2011 at 19:47, Boris Zbarsky bzbar...@mit.edu wrote:
A comment on use cases that was brought up over here.
There's a use case that is not addressed by XBL1 and impossible to quite
address in a JS library that goes as follows. Say you have some data in a
table. Semantically
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
11 matches
Mail list logo
