In the attached testcase generated content should be a block with beige
background and border. Though is declared as display:block, generated content is
rendered as inline.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
border:1px solid #999;
<span expl="This should
as one block.">foo</span>
Created attachment 143590 [details]
> Though is declared as display:block, generated content is
> rendered as inline.
Our behavior is correct per
But it looks like in CSS2.1 that whole section on what properties are not
applied to generated content, etc, has been removed. If so, we need to remove
some code in nsRuleNode.cpp...
Adam, can you please file a separate bug on the wrapping weirdness in that testcase?
> Our behavior is correct per
Okay, I didn't look to CSS 2.0 specification neither following resolution of bug
BTW Opera 7.50 PR 3 is rendering this testcase as CSS 2.1 says.
> Adam, can you please file a separate bug on the wrapping weirdness in that
I'm sorry, but I don't see any wrapping weirdness =) I wrote attribute value
with line breaks and I hope that Mozilla will display it with white-space:pre;
same on several lines. Or do you mean something completely different?
Ah, I missed white-space:pre.
Yeah, position, float, display, white-space, etc, they all apply to ::before and
::after now. In fact about the only thing that _doesn't_ apply is 'binding'.
There's an example at http://www.howtocreate.co.uk/wrongWithIE/eightpointbox.html that shows some of what can be done if position and related properties can be applied to generated content. Compare the Firefox 1.5 and Opera 8.5 renderings.
We're aware what the problem is, yes.
This works (fixed by bug 238072?)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081011 Minefield/3.1b2pre