- From: Rainer Åhlfors <rahlfors@wildcatsoftware.net>
- Date: Fri, 2 Mar 2007 10:43:28 -0700
- To: <www-style@w3.org>, <bzbarsky@MIT.EDU>
I will agree that it is a problem with the spec as written. Specifically this part: "A clipping region defines what portion of an element's rendered content is visible." It essentially implies that the area outside the clipping region is treated as 'visibility: hidden'. This explains the presence of scroll bars. While I agree that the behavior is not desirable, and that this portion of the spec should be re-written to indicate this, I would in fact maintain my position that it is not a _browser_ bug. The browsers seem to handle the scenario exactly as you would expect, given the information presented within. Be they Gecko layout developers or not, and CSS WG members or not -- the spec as written today supports the behavior of the browsers. Hence, it is not a browser bug. That's all I was saying. -----Original Message----- From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] Sent: Friday, March 02, 2007 10:31 AM To: rahlfors@wildcatsoftware.net Subject: Re: Expected overflow behavior for element with clip set? Rainer Åhlfors wrote: > http://www.w3.org/TR/REC-CSS2/visufx.html#overflow > Initial value of 'overflow': 'visible' > > http://www.w3.org/TR/REC-CSS2/visufx.html#clipping > The 'clip' property applies to elements that have a 'overflow' property with > a value other than 'visible'. Sure. But Eli's test behaves the same if you set "overflow" on the child. > Not to mention the fact that you are defining a height and width for the > child element. Why does that matter in this case? > This is not a bug or a problem. Well. The three lead Gecko layout developers (one of whom is a CSS Working Group member) all thought this is a problem with the spec as written when Eli asked us about it. Hence his mail to the group. -Boris
Received on Friday, 2 March 2007 17:42:38 UTC