- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 14 Dec 2009 18:42:33 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8491
Summary: Using "Window" for this interface is very unfortunate.
That word is heavily overloaded and it is already
"taken" by javascript. The API documentation here
illustrates the issue: note the attribute 'window' of
type WindowProxy. In all kinds of discussions
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-
work/#windows
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
Section: http://www.whatwg.org/specs/web-apps/current-work/#windows
Comment:
Using "Window" for this interface is very unfortunate. That word is heavily
overloaded and it is already "taken" by javascript. The API documentation here
illustrates the issue: note the attribute 'window' of type WindowProxy. In all
kinds of discussions we have to spend time clarifying what we mean by the
window property of the Window interface and oh by the way it's a WindowProxy.
type not a window type. Ultimately the reason WindowProxy was introduced was
to deal with previous failings to clearly identify the roles of window-like
objects. Based on a quick read of the document here, the interface is
BrowsingContext. That is, now that you look back at the document with a fresh
mind, the interface named "Window" should really be called BrowsingContext.
Then the API and document is clearer.
Posted from: 198.4.83.52
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 14 December 2009 18:42:35 UTC