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 20:32:44 +1100
To: public-webapi@w3.org
Message-ID: <20060322093244.GE22949@port.mcc.id.au>

Maciej Stachowiak:
> Requiring the Window to be the defaultView is supposed to imply this  
> for CSS UAs, but think it would also be OK to add a conditional  
> requirement to Window:
> "In user agents that support the ViewCSS interface from DOM Level 2  
> Style, Window objects MUST implement the ViewCSS interface."
> Test case:
> shouldBeTrue("!document.getOverrideStyle || window.getComputedStyle");
> I think this is arguably redundant with DOM Level 2 Style though...
> DOM Level 2 Views says:
> "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."
> Granted this is a bit ambiguous, but I think "an instance" is  
> supposed to mean "any instance", not "some unspecified instance".

Ok, I think I was perhaps misunderstanding the role of the ViewCSS
interface now that I think about it.  ViewCSS is meant to augment an
existing view to provide access to computed style information about that
view of the document, rather than being a view solely by itself.  Is
this correct?

> The Window draft says:
> "Each view of a Document presented in a browsing context must be  
> represented by an object that implements the Window interface."
> This is intended to require that any AbstractView instance for such a  
> Document must also implement Window. Granted this could be more clear.

I think this sentence isn't too unclear.

 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 09:33:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:20 UTC