RE: Cascading Style Sheets

None of these issues should exist in a CSS-P/ CSS1 compliant
implementation. 

We have finished our CSS-P implementation for IE4 Beta 2 that will be
available this month.

Let me know if the following are addressing your questions.

1) <DIV STYLE="position: absolute; top: 10pt; left: 10px; width: 10em;
height: 100px; background: red;border: 2pt gray inset"><DIV>
This displays a box with the background and border at the specified
dimension. This box can also sit on top of or behind the text by setting
the css z-index property (negative values put the positioned element
behind the text, positive z-index goes on top of the text)

2) You get much more clip and overflow support:
clip: rect(top bottom right left) 
overflow: scroll | visible | hidden | auto

Clip works very similar to the attribute of the same name on the Layer
tag but supports percentages, em, pt, etc (all the CSS units)

Overflow is cool because you can cause scrollbars to appear if the
content does not fit in the box, you can cause the contents to only
display scrollbars if necessary (auto), visible automatically grows the
positioned element for the contents, and hidden clips the contents at
the specified size. 

3) CSS has a "background" property that is very flexible. You can tile
the image, repeat it horizontally, vertically, position it at an
explicit location in the element (eg., bottom right), specify a fallback
color and more. These can be transparent gifs, png images, animated
gifs, etc. All of these features are defined in the CSS 1 specification.


In addition, every property can be scripted through IE4's Dynamic HTML
object model (for swipe effects, moving elements, accessing and changing
the contents, changing the appearance, etc) but that is independent from
CSS.

Scott Isaacs
Program Manager
IE4 Team

> ----------
> From: 	Gregory Houston[SMTP:vertigo@triberian.com]
> Reply To: 	vertigo@triberian.com
> Sent: 	Thursday, July 03, 1997 9:31 AM
> To: 	www-style@w3.org
> Subject: 	Cascading Style Sheets
> 
> I have noticed a couple benefits of using Netscape's <layer>s tags
> over
> using CCS positioning. I hope that you might consider taking these
> into
> consideration when you make the next revision of CCS.
> 
> 1. I don't have to use <table>s with Netscape's <layer>s. With
> <layer>s
> if I define a layer as 128 x 128 pixels with a red background, thats
> exactly what I get. But with CCS, nothing will show up until I put
> some
> content in the layer, and then the red background color will only
> appear
> around the text. Thus I still have to fool with <table>s if I want to
> use CCS. And ... thus, I'll be sticking with Netscape's <layer> tag
> until this is fixed.
> 
> 2. Netscape has a much better system of dealing with clipping. I have
> yet to get what I want with CCS positioning. But with <layer>s I have
> full control to animate the clipping. This is much more powerful than
> merely animating the width and height of a layer.
> 
> 3. This part I'm not sure about, but so far I have not been able to
> add
> a background image to my CSS layers. I can do so very easily with
> <layer>s, and those background images can be transparent gifs.
> 
> Thank you for your time,
> -- 
> Gregory Houston                 Triberian Institute of Emotive
> Education
> vertigo@triberian.com           http://www.triberian.com 
> phone:    816.561.1524          info@triberian.com
> cellular: 816.807.6660          snail: PO Box 32046 Kansas City MO
> 64171
> ICQ UIN:  840273
> 
>      "Empowered, impassioned, we have a lust for life insatiable!"
>

Received on Thursday, 3 July 1997 14:18:04 UTC