W3C home > Mailing lists > Public > www-style@w3.org > January 2008

Re: Section 10.3.8 really needs to be fixed

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sat, 26 Jan 2008 23:10:25 -0800
Message-ID: <479C2E61.7040105@inkedblade.net>
To: David Hyatt <hyatt@apple.com>
CC: CSS <www-style@w3.org>

David Hyatt wrote:
> 
> This compliance change we made in WebKit to match section 10.3.8 of 
> CSS2.1 continues to cause problems on the real-world Web.  We've gotten 
> numerous bugs on this issue, and I've brought this up before.
> 
> http://www.w3.org/TR/CSS21/visudet.html#abs-replaced-width
> 
> http://bugs.webkit.org/show_bug.cgi?id=16975
> 
> The spec is just plain wrong.  The results it gives don't match the 
> common sense rendering that Web site authors would expect for:
> 
> <iframe style="position:absolute;left:0;top:0;right:0;bottom:0"></iframe>
> 
> If I specify a top, bottom, right and left of 0, then why on earth 
> should the object's intrinsic width or height override?  It's completely 
> counter-intuitive that you can't use this pattern to stretch an iframe 
> or image in CSS2.1.
> 
> Note that Firefox 3 even interprets the spec very literally and doesn't 
> stretch in the left/right case but does in the top/bottom case (this 
> behavior is even crazier IMO).
> 
> This section of the spec needs to be amended.

1. It would be useful if you could post the URL of a testcase.
2. We'll need test results for at least the latest releases of Safari, IE,
    Mozilla, Opera.
3. I personally have no opinion on this, other than that whatever change we
    make must not affect the current set of computations when 'auto' margins
    are involved.

~fantasai
Received on Sunday, 27 January 2008 07:10:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:00 GMT