By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,396 Members | 1,882 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,396 IT Pros & Developers. It's quick & easy.

What parts of CSS 2.1 specification really implemented

P: n/a
Hello All.

I wonder if browsers developers scoff at CSS developers... I do simple
tests while reading CSS2.1 specification, just few boxes. And from time
to time I see that recent browsers render these *simple* things
*incorrectly* (each one in it's own way).

If I had a big page with dozen of blocks and they rendered incorrectly
- I'll call this a *bug* (and I can understand this). But when simple
things from specification not working - I don't know how too call
this...

I just took an ACID2 test with IE6, IE7, Opera 9, Firefox 2.0.0
http://www.webstandards.org/action/acid2

Opera 9 is excellent on this test, Firefox good (but has errors),
IE6/IE7 - terrible.

Can any body point me to resources, where I can read what parts of CSS
2.1 specification really implemented, and what are not?

Also, may be there is a resource that illustrates CSS2.1 expected
rendering (for every element). May be some wiki, or unit tests?

- Alex

Jan 22 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On 2007-01-22, fo***********@gmail.com <fo***********@gmail.comwrote:
Hello All.

I wonder if browsers developers scoff at CSS developers...
Probably, they're a pretty arrogant bunch.
I do simple tests while reading CSS2.1 specification, just few boxes.
And from time to time I see that recent browsers render these
*simple* things *incorrectly* (each one in it's own way).
In many cases the specification allows browsers to render things
differently. Just because they do isn't evidence of non-conformance or
bugs, although it's often worth investigating.
If I had a big page with dozen of blocks and they rendered incorrectly
- I'll call this a *bug* (and I can understand this). But when simple
things from specification not working - I don't know how too call
this...
Next time you find one post a specific example.
I just took an ACID2 test with IE6, IE7, Opera 9, Firefox 2.0.0
http://www.webstandards.org/action/acid2

Opera 9 is excellent on this test, Firefox good (but has errors),
IE6/IE7 - terrible.
That acid test is diabolical.
Can any body point me to resources, where I can read what parts of CSS
2.1 specification really implemented, and what are not?
There's not much of the spec that isn't implemented in Opera and
Firefox. The most notable thing missing from Firefox is
display:inline-block.
Jan 22 '07 #2

P: n/a
Ben C wrote:
There's not much of the spec that isn't implemented in Opera and
Firefox. The most notable thing missing from Firefox is
display:inline-block.
Display:run-in! I want display:run-in!

Sigh.

David
Stardate 7060.7
Jan 22 '07 #3

P: n/a
On 2007-01-22, David Trimboli <da***@trimboli.namewrote:
Ben C wrote:
>There's not much of the spec that isn't implemented in Opera and
Firefox. The most notable thing missing from Firefox is
display:inline-block.

Display:run-in! I want display:run-in!
I completely forgot about display: run-in! I just tried it and it seems
to basically work in Opera, but not Firefox.

I never realized though how useful inline-block was. Quite a few times
people have posted layout requirements here and the solution has
involved the words "now if only inline-block was better supported..."
Jan 22 '07 #4

P: n/a
Rik
Ben C wrote:
On 2007-01-22, David Trimboli <da***@trimboli.namewrote:
>Ben C wrote:
>>There's not much of the spec that isn't implemented in Opera and
Firefox. The most notable thing missing from Firefox is
display:inline-block.

Display:run-in! I want display:run-in!

I completely forgot about display: run-in! I just tried it and it
seems to basically work in Opera, but not Firefox.
Opera Rocks!
I never realized though how useful inline-block was. Quite a few times
people have posted layout requirements here and the solution has
involved the words "now if only inline-block was better supported..."
Yup, width (and/or height), without the irritating properties of floating
(they _are_ contained within the box, instead of
'floated out', which usually makes us do otherwise unnecessary clears to
let the box contain them...
--
Rik Wasmus
Jan 22 '07 #5

P: n/a
Hi,

Thanks for your replies.
>The most notable thing missing from Firefox is display:inline-block.
Yes, inline-block bugs and 'acid2' motivated me too write the post.
That acid test is diabolical.
May be, but rendering as IE7 is diabolical too, is not it? Or may be my
IE7 is not final?
There's not much of the spec that isn't implemented in Opera and
Firefox.
Hm... Cool if so.
Can you also check following HTML. It seems that 'display' value
affects div rendering only under Opera (neither FF nor IE7).

= = = = = = =
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
<html>
<style type="text/css">

div, span {
background:orange; border:1px gray solid; padding:4px; margin:2px;
display: inline-block;
}

</style>

<body>
<p>
<strong>inline</strong>
<div>div</div>
<div>div</div>
<br>
<span>span</span>
<span>span</span>
</p>
</body>

</html>
= = = = = = =

Is it a bug? If so we have bug in: inline, inline-block, run-in... If
my CSS learning continue this way I'll have only 'display:none' in my
toolbox :-)

- Alex.

Jan 23 '07 #6

P: n/a
On 2007-01-23, fo***********@gmail.com <fo***********@gmail.comwrote:
Hi,

Thanks for your replies.
>>The most notable thing missing from Firefox is display:inline-block.
Yes, inline-block bugs and 'acid2' motivated me too write the post.
>That acid test is diabolical.
May be, but rendering as IE7 is diabolical too, is not it? Or may be my
IE7 is not final?
I don't know about IE7. People seem to be saying it's an improvement
over IE6, but I get the impression it's a long way behind Firefox.
>There's not much of the spec that isn't implemented in Opera and
Firefox.
Hm... Cool if so.
Can you also check following HTML. It seems that 'display' value
affects div rendering only under Opera (neither FF nor IE7).
This is just because they don't support display: inline-block. You can
change display on a div to display: inline (for example) and you will
see the difference.
>
= = = = = = =
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
<html>
<style type="text/css">

div, span {
background:orange; border:1px gray solid; padding:4px; margin:2px;
display: inline-block;
}
[snip]
Is it a bug? If so we have bug in: inline, inline-block, run-in... If
my CSS learning continue this way I'll have only 'display:none' in my
toolbox :-)
Don't count on display:none working :)
Jan 23 '07 #7

P: n/a
fo***********@gmail.com schrieb:
<p>
<strong>inline</strong>
<div>div</div>
<div>div</div>
<br>
<span>span</span>
<span>span</span>
</p>
[...]
Is it a bug? If so we have bug in: inline, inline-block, run-in...
.... and in your code: p elements cannot contain div elements.
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)
Jan 23 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.