Re: CSS WG - Pulling Back the Curtains

Ah thanks.   That was an accident.  My autocomplete prefers the  
private when i hit "w". :)

dave

On Mar 28, 2008, at 2:09 PM, Garrett Smith wrote:

>
> (I'm not on the w3c internal list -> back to the public list)
>
>
> ---------- Forwarded message ----------
> From: Garrett Smith <dhtmlkitchen@gmail.com>
> Date: Fri, Mar 28, 2008 at 12:07 PM
> Subject: Re: CSS WG - Pulling Back the Curtains
> To: David Hyatt <hyatt@apple.com>
> Cc: w3c-css-wg@w3.org
>
>
> On Fri, Mar 28, 2008 at 11:57 AM, David Hyatt <hyatt@apple.com> wrote:
>> On Mar 28, 2008, at 1:41 PM, Garrett Smith wrote:
>>
>>> On Fri, Mar 28, 2008 at 11:37 AM, David Hyatt <hyatt@apple.com>  
>>> wrote:
>>>> On Mar 28, 2008, at 11:54 AM, Garrett Smith wrote:
>>>>
>>>>> In safari 3.1, this doesn't even work:-
>>>>> document.defaultView.getComputedStyle(el,
>>>>> '').getPropertyValue('left')
>>>>>
>>>>
>>>> http://bugs.webkit.org/
>>>>
>>
>> Ok, so bug http://bugs.webkit.org/show_bug.cgi?id=18175 is the one  
>> you
>> filed.
>>
>> The object in question is not positioned, so we return "auto" as the
>> computed value.  Is that actually incorrect?  If you positioned it,  
>> we
>> would then return 100px.
>
> Read the bug rep't. Click the attachment -> view source.
>
>
>
>
>>
>> We don't return the original back end CSS value if the front end  
>> value
>> ends up resolving to something different.  (We do the same with z-
>> index on an unpositioned element as well for example.)  Maybe this is
>> a bug.  I'm not sure.  Perhaps others could comment.
>>
>> However, I hardly think it's the major issue you're making it out to
>> be, since in the absence of positioning those values would be ignored
>> when rendering anyway.
>>
>> dave
>> (hyatt@apple.com)
>>
>>
>

Received on Friday, 28 March 2008 19:12:37 UTC