This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
E.g. div class="poem" when rendered becomes div style="font-variant: small-caps" Is that deliberate?
Good catch! http://dvcs.w3.org/hg/webcomponents/rev/06d6e47f2848
It was deliberate. The reason is that decorators specify a rendering, not markup per-se. So I was trying to use DOM as a way to specify rendering, hence the note about "not including UA stylesheets." But maybe that is too subtle. Maybe the example should include an image of what is produced, perhaps with rectangles highlighting which boxes are contributed by the document and which are contributed by the decorator. I think it is good pedagogy to reinforce the notion that decorators don’t produce DOM.
(In reply to comment #2) > It was deliberate. The reason is that decorators specify a rendering, not > markup per-se. So I was trying to use DOM as a way to specify rendering, hence > the note about "not including UA stylesheets." But maybe that is too subtle. Interesting. But even from CSS perspective, the class name is still there, right?
I guess the class name is still "there", but think of it more as a reftest expected result. Maybe it should be replaced with a diagram and not markup. Or we could invent textual syntax for rendered blocks.
(In reply to comment #4) > I guess the class name is still "there", but think of it more as a reftest > expected result. Maybe it should be replaced with a diagram and not markup. Or > we could invent textual syntax for rendered blocks. Sounds good. Can you file a bug? I'll fix up next time I sweep up explainer bugs.
I look at this again and I think it is fine as-is. I removed the note about omitting user agent styles, since they are obviously implied by "as if it was this markup" <https://dvcs.w3.org/hg/webcomponents/rev/9cb2dca32e6b>