W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css-regions] Invalid access in NamedFlowCollection

From: Alan Stearns <stearns@adobe.com>
Date: Wed, 29 Aug 2012 13:34:03 -0700
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CC63CA8F.120AF%stearns@adobe.com>
On 8/29/12 9:53 AM, "Boris Zbarsky" <bzbarsky@MIT.EDU> wrote:

>On 8/29/12 12:46 PM, Mihai Balan wrote:
>> Currently the spec says that should a script try to retrieve an
>> inexistent object from a NamedFlowCollection, either by using an
>> out-of-range index or an invalid name, it should return **null**.
>>
>> I think it would be better to return **undefined** instead, for a couple
>> of reasons:
>>
>> ·Currently all JavaScript and HTMLCollection-s return **undefined** for
>> invalid keys (e.g. Array, document.forms, document.querySelectorAll() )
>>
>> ·Also, in general, null doesnıt mean that thereıs nothing there, but
>> actually that something might be there, but itıs not a definite object
>>(yet)
>>
>> Anyone has any thoughts on this?
>
>Won't you get the "undefined" behavior for free if you use sane
>definitions of the supported names and indices in your prose?
>
>I agree that the undefined behavior is better, btw: it also makes "in"
>work correctly and such.

I agree as well. I've made the change.

Thanks,

Alan
Received on Wednesday, 29 August 2012 20:34:29 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:59 GMT