- From: Matt Giuca <notifications@github.com>
- Date: Tue, 31 Mar 2020 18:34:14 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 1 April 2020 01:34:27 UTC
Yeah, I don't want to use `Window` just because it pollutes the global namespace. I think it's important to consider sometimes that the mechanics of these things can be more important than the names. Even if "window" is the right name for this, it's mechanically problematic. These things go way way back to the history of the web, so the best thing to do is shrug and say "they have the wrong names, for historical reasons". Modern web design should consider `Window` to mean "the global top-level namespace" and `Document` to mean "the object that represents the current document *and* its window". New APIs should only go in `Window` if they're fundamental things that should be available automatically, like a new array type, not a new API that will be called in one very special place across the entire site. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/387#issuecomment-606974140
Received on Wednesday, 1 April 2020 01:34:27 UTC