- From: Kristopher Giesing <kris.giesing@gmail.com>
- Date: Mon, 19 May 2014 10:17:30 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: "public-fx@w3.org" <public-fx@w3.org>
Received on Monday, 19 May 2014 17:17:57 UTC
I guess I am thinking of this as being more of an intrinsic property, like the children of a DOM node. This is expected to change over time, but semantically it always exists and is owned by a specific parent object. If on the other hand the semantics are more like getElementsByTagName, where ownership is spread out among many parents and the method is performing a collection operation across them, then it makes more sense to have an object-creator. (It occurs to me that my objection about get* creating new objects already has plenty of counter-examples in the DOM.) With these semantics having the list be live seems counter-intuitive and possibly hard to implement - it becomes something like jQuery's "live" event registration. - Kris On Mon, May 19, 2014 at 10:06 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 5/19/14, 1:05 PM, Kristopher Giesing wrote: > >> Let me rephrase: it would make more sense to me to provide an >> object-getter for this task than an object-creator >> > > And this would then be a live object of some sort? > > -Boris >
Received on Monday, 19 May 2014 17:17:57 UTC