- From: Jim Ley <jim.ley@gmail.com>
- Date: Tue, 14 Feb 2006 11:05:53 +0000
- To: "public-webapi@w3.org" <public-webapi@w3.org>
On 2/14/06, Anne van Kesteren <annevk@opera.com> wrote: > On Tue, 14 Feb 2006 11:48:31 +0100, Mark Birbeck <mark.birbeck@x-port.net> > wrote: > > Why a 'window' object? Many of these features are independent of a > > 'window', > > and would be better placed on another object...perhaps an application > > object, or something. Also, many classes of applications that could use a > > DOM and the features mentioned here, don't need a 'window'. > > Because our charter was designed with compat in mind. I think even more importantly than that, it's that the label is widely understood by the audience. Things like "DOM Level 3.0 abstractView" is gibberish to most people. We all know that the labels themselves carry no meaning alone, we could call it object_67 and then have property_1, property_2 etc. but we don't because we pick labels that aid understanding. window does that very well. Cheers, Jim.
Received on Tuesday, 14 February 2006 11:06:05 UTC