Re: [widgets-twi] window object

[Scott Wilson]

On 9 Feb 2010, at 09:22, Marcos Caceres wrote:

On Tue, Feb 9, 2010 at 9:54 AM, Cyril Concolato <cyril.concol...@enst.fr > wrote:

Le 08/02/2010 13:29, Robin Berjon a écrit :

On Feb 5, 2010, at 16:18 , Marcos Caceres wrote:

 wrote:

On Thu, Feb 4, 2010 at 6:41 PM, Cyril Concolato<cyril.concol...@enst.fr >

that does not support the window object ?

So I'm wondering how should the widget object be implemented in a UA

Yeah, that's a tough one... the spec says:


implements the widget interface to author scripts."

"For a widget instance, a user agent MUST expose a unique object that It does not give any guidance as to how the interface must be exposed.

But then again, SVG supports the Window object (minimally defined in

http://www.w3.org/TR/SVGMobile12/svgudom.html#dom__Window). So just adding a

widget field there ought to be straightforward.

specify. What's the benefit of using the window object?

My mistake. I had not realized that. But again, the question is why put the widget object on the window object, apart from it being a black hole. Why not put it in the global object. What's wrong with that? It would easier to

I don't think there is a way around this. Everything lives in the
window: it is the top level scope. This is evident by running
"<script>alert(this)</script>", which returns [object Window] or
[object DOMWindow]. Changing this to have Widget as the top or as a
shared top level scope would break code expecting to window object to
be there. Also, it might not even be possible to have two objects be
at the level scope at the same time.

S

In Wookie we just create the widget object in the global scope, and then add it as an attribute to the window object. Author scripts can access it either by "window.widget" or just plain "widget". I wonder though - for authors what should we recommend if they want their widget to run unmodified in the most UAs?

smime.p7s
Description: S/MIME cryptographic signature