This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8491 - 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
Summary: Using "Window" for this interface is very unfortunate. That word is heavily o...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-14 18:42 UTC by contributor
Modified: 2010-10-04 14:57 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-12-14 18:42:33 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2009-12-14 18:56:33 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The term Window is used precisely _because_ it is "taken" by JavaScript. It's the same use of the same term.