- From: Andrew Fedoniouk <news@terrainformatica.com>
- Date: Sat, 2 Oct 2004 12:12:53 -0700
- To: "Brian Sexton" <discussion-w3c@ididnotoptin.com>
- Cc: "www style" <www-style@w3.org>
|...but the current state of CSS implementations--as evidenced by the | age of some CSS bugs in browsers--is not encouraging. Right. CSS21: "For this specification to exit the CR stage, the following conditions must be met: 1.There must be at least two interoperable implementations for every feature..." E.g. there are 15 values in 'display' attribute. Only four of them (CSS1: none, block, inline, list-item) work somehow more than in two UAs. So, for the time being, CSS level 1 (W3C Recommendation 17 Dec 1996, revised 11 Jan 1999) is the Recommendation. About dispaly: table-*. Being applied will dramaticly modify underlying DOM. Too artificial and complex in interpretation and in implementation. Plus it seems nobody really needs them. My guess: will not be implemented. About dispaly: inline-block. In fact can be applied only to pure <span> alike elements. Other use cases are just not allowable by HTML Rec. My guess: will not be used even being implemented. Andrew Fedoniouk. http://terrainformatica.com | | > | ... Opera is a notable exception. | > | > Try to open http://terrainformatica.com/w3/block-inline.htm then. | > I wouldn't consider still this as a support of inline-block. | > (no offence to Opera developers, in fact - my deepest and honest respect | > to | > them) | | Hopefully support for inline-block will improve all-around (or be | implemented where it has not been already) soon, but I will not hold my | breath. I like to think that all of this standards discussion is for | something, but the current state of CSS implementations--as evidenced by the | age of some CSS bugs in browsers--is not encouraging. | | | Cheers, | | Brian Sexton | | |
Received on Saturday, 2 October 2004 19:13:39 UTC