W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

Re: DOM Views confusion

From: Cameron McCormack <cam@mcc.id.au>
Date: Wed, 22 Mar 2006 17:30:50 +1100
To: public-webapi@w3.org
Message-ID: <20060322063050.GD22949@port.mcc.id.au>

Ian Hickson:
> Well, it doesn't have to be ViewCSS. The expectation is that an instance 
> of the ViewCSS interface can be obtained by using binding-specific casting 
> methods on an instance of the AbstractView interface (Window being one 
> such instance). It only applies to CSS UAs, not all Window UAs need 
> implement CSS.

So I guess my problem is with the language "on an instance of the
AbstractView interface".  This doesn't imply that all AbstractViews need
to implement ViewCSS, just that there needs to be one AbstractView that
can be casted to a ViewCSS.

> > Ok, but at the moment I don't see anything that requires ViewCSS to be 
> > implemented on the same object as Window.
> 
> ViewCSS is from AbstractView:
> 
>    http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-ViewCSS
> 
> Window is an AbstractView (per Window or WHATWG).

Sure, but that doesn't mean that both need to be implemented on the same
object--it just means that ViewCSS is a type of view, and Window is also
a type of view.

> Ah. Well, ViewCSS and Window are on the same object.

Please show me some text that states explicitly that if a document has a
ViewCSS view and a Window view then they need to be the same object.
Perhaps I am being obtuse, but I cannot find it myself...

Thanks,

Cameron

-- 
 Cameron McCormack			ICQ: 26955922
 cam (at) mcc.id.au			MSN: cam (at) mcc.id.au
 http://mcc.id.au/			JBR: heycam (at) jabber.org
Received on Wednesday, 22 March 2006 06:31:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT