:after generated content cannot receive some CSS properties,
including 'position', 'float', list properties, and table properties.
That's CSS2. Can't find that line in CSS2.1.
That's possible, I quoted this from PIE thus I don't know whether it was
ment as a normative restriction, or
I've been playing with :after lately, although not for anything serious.
I've had some problems with positioning in Gecko.
:after generated content cannot receive some CSS properties, including
'position', 'float', list properties, and table properties.
---
Jan Brasna wrote:
:after generated content cannot receive some CSS properties,
including 'position', 'float', list properties, and table
properties.
That's CSS2. Can't find that line in CSS2.1.
This seems to open for a bit more real use:
The :before and :after pseudo-elements elements
On 12 Oct 2005, at 8:48 am, Gunlaug Sørtun wrote:
Jan Brasna wrote:
:after generated content cannot receive some CSS properties,
including 'position', 'float', list properties, and table
properties.
That's CSS2. Can't find that line in CSS2.1.
All those properties are perfectly fine in CSS
Philippe Wittenbergh wrote:
?? margin seems to work perfectly fine here. Both on Firefox 1.6a1
nightly trunk build and Firefox 1.5beta 2
http:dev.l-c-n.com/_temp/after.php (the word blah in a grey box
after each paragraph, and the word 'the End' as body:after)
Working at my end too - once I
On 12 Oct 2005, at 1:00 pm, Gunlaug Sørtun wrote:
Philippe Wittenbergh wrote:
?? margin seems to work perfectly fine here. Both on Firefox 1.6a1
nightly trunk build and Firefox 1.5beta 2
http:dev.l-c-n.com/_temp/after.php (the word blah in a grey box
after each paragraph, and the word 'the
Zach Inglis wrote:
I wanted to know your opinion on my post http://www.zachinglis.com/
websites/website/before-sliding-doors/.
Interesting.
I've been playing with :after lately, although not for anything serious.
I've had some problems with positioning in Gecko. Opera is doing fine.
Would be
