- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 9 Jan 2004 18:02:26 +0000 (UTC)
- To: fantasai <fantasai@escape.com>
- Cc: www-style@w3.org
On Tue, 4 Nov 2003, fantasai wrote: > > http://www.w3.org/TR/2003/WD-CSS21-20030915/visufx.html#overflow-clipping > > # An element's height exceeds an explicit height assigned > # to the containing block (i.e., the containing block's > # height is determined by the 'height' property, not by > # content height). > > An explicit height on the containing block can cause > overflow even if each individual descendant has a height > that is less than the containing block; it's the position > of the bottom edge of the box that's important. ...and: > # - A descendent box is positioned absolutely, partly > # outside the box. Such boxes are not clipped by the > # overflow property on their ancestors. > # - A descendent box has negative margins, causing it > # to be positioned partly outside the box. > > What about relatively positioned boxes? These are just examples. (The list starts with "e.g.".) > # In the following example, pressing either form button > # invokes a user-defined script function > > user-defined or author-defined? It's a hypothetical script language, who knows! ;-) (Assigned issue 252.) > You might want to make the manipulation of CSS properties > more explicit. The show and hide functions don't say anything > about CSS. True. Hopefully the point is clear enough. More examples will hopefully be given in DOM-related specs later. -- Ian Hickson )\._.,--....,'``. fL U+1047E /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 9 January 2004 13:02:27 UTC