W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: [widgets-twi] window object

From: Robin Berjon <robin@berjon.com>
Date: Mon, 8 Feb 2010 17:20:16 +0100
Cc: cyril.concolato@telecom-paristech.fr, public-webapps <public-webapps@w3.org>
Message-Id: <84C5E953-A979-4B39-B578-EE62525B9FDD@berjon.com>
To: Marcos Caceres <marcosc@opera.com>
On Feb 8, 2010, at 13:51 , Marcos Caceres wrote:
> As much as I dislike it, I'm also not that inclined to define what to do for non-"Window"-based implementations (beyond what we currently have in the spec; which, I admit, is not much).

I don't think that we could even if we wanted to. Presumably, any technology that embeds Javascript will have to have defined a global object of some form or other (I don't see how it works otherwise) but the exact details will either 1) be copied from HTML or 2) be something different that we can't predict. So for (1) it'll be obvious what to do, for (2) it's obvious that we can't do anything to help.

> It is, non-the-less, kinda bad that we don't have a spec that defines Window independently of HTML but I understand why that is: because Window is a foul intertwined incestuous mess...

Actually, the reason is because we don't have an editor for it. If we did, Window could get split out of HTML (as it used to be).

> Also, the main use cases we are dealing with all rely on Window being there (HTML and, as Robin points out, SVG). If UAs start to emerge that are windowless (e.g., "daemon" or "headless" widgets), then we should formally define how this binds to some top-level context. WDYT?

Yeah, but we can cross that bridge if and when we get there.

-- 
Robin Berjon - http://berjon.com/
Received on Monday, 8 February 2010 16:20:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:36 GMT