I was writing this morning when it occurred to me that we throw the word “window” around a lot, and it has two meanings. New Web developers may not understand that, and we may need to do more to help ensure that confusion doesn’t arise.
The first meaning is the obvious: a window is the user interface construct of a view, usually movable, which may have elements like scroll bars, close boxes, and others in its frame area, with a document or other content within.
The other meaning is the content object represented by the DOM Window
interface. Once upon a time, this was the code representation of that same UX apparatus, but it’s not anymore. Window
really represents an abstraction that comingles specific attributes of a physical window with those of a browser tab, since a tab is the true parent container of a document nowadays.
The latter explanation is one that we may need to do better at clarifying for new developers. Almost every time we say “window”, we actually mean “tab”, even though a tab is in essence represented by the Window
interface.
Any thoughts on (a) how to best describe this concept and (b) how to go about ensuring that new developers understand this? Or is this a non-issue (I don’t think it is, but I could be mistaken).
Eric Shepherd
Senior Technical Writer
MDN Web Docs: https://developer.mozilla.org/
Blog: http://www.bitstampede.com/
Twitter: http://twitter.com/sheppy