DOM 2 Views

Hi all,

in http://www.w3.org/Bugs/Public/show_bug.cgi?id=9336 there is a
proposal to "Remove concept of views" and move the property of
AbstractView to HTML5's Window and the property of DocumentView to
HTMLDocument.

Pretty much everyone implements AbstractView and DocumentView [1][2] in 
some way and since those interfaces are trivial I don't quite see the
reason for the proposed change.

DOM 2 Views has one practical advantage. It allows other
specifications to refer to AbstractView (which is in practice the
Window object). That way other specifications don't need to refer to
unstable HTML5's Window.
AbstractView is used this way for example in DOM 3 Events.

So, I wonder what is the reason for proposed change?
The bug report certainly doesn't explain that.

Although it may sound a bit strange to keep D2V alive just
because of AbstractView, I see it pretty practical way
to allow other specifications to refer to Window without actually
taking in all the HTML5 baggage.



-Olli


[1] 
http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/views/nsIDOMDocumentView.idl
[2] http://trac.webkit.org/browser/trunk/WebCore/dom/Document.idl#L103

Received on Monday, 12 April 2010 10:43:53 UTC