A popup window is one of the oldest methods to show additional document to user.
Basically, you just run:
… And it will open a new window with given URL. Most modern browsers are configured to open new tabs instead of separate windows.
In the past evil sites abused popups a lot. A bad page could open tons of popup windows with ads. So now most browsers try to block popups and protect the user.
Most browsers block popups if they are called outside of user-triggered event handlers like
This way users are somewhat protected from unwanted popups, but the functionality is not disabled totally.
What if the popup opens from
onclick, but after
setTimeout? That’s a bit tricky.
Try this code:
The popup opens in Chrome, but gets blocked in Firefox.
…If we decrease the delay, the popup works in Firefox too:
The difference is that Firefox treats a timeout of 2000ms or less are acceptable, but after it – removes the “trust”, assuming that now it’s “outside of the user action”. So the first one is blocked, and the second one is not.
For instance, many shops use online chats for consulting people. A visitor clicks on the button, it runs
window.open and opens the popup with the chat.
Why a popup is good here, why not in-page?
- A popup is very simple to attach to a site, little to no overhead. It’s only a small button, without additional scripts.
- A popup may persist even if the user left the page. For example, a consult advices the user to visit the page of a new “Super-Cooler” goodie. The user goes there in the main window without leaving the chat.
The syntax to open a popup is:
window.open(url, name, params):
- An URL to load into the new window.
- A name of the new window. Each window has a
window.name, and here we can specify which window to use for the popup. If there’s already a window with such name – the given URL opens in it, otherwise a new window is opened.
- The configuration string for the new window. It contains settings, delimited by a comma. There must be no spaces in params, for instance:
left/top(numeric) – coordinates of the window top-left corner on the screen. There is a limitation: a new window cannot be positioned offscreen.
width/height(numeric) – width and height of a new window. There is a limit on minimal width/height, so it’s impossible to create an invisible window.
- Window features:
menubar(yes/no) – shows or hides the browser menu on the new window.
toolbar(yes/no) – shows or hides the browser navigation bar (back, forward, reload etc) on the new window.
location(yes/no) – shows or hides the URL field in the new window. FF and IE don’t allow to hide it by default.
status(yes/no) – shows or hides the status bar. Again, most browsers force it to show.
resizable(yes/no) – allows to disable the resize for the new window. Not recommended.
scrollbars(yes/no) – allows to disable the scrollbars for the new window. Not recommended.
There is also a number of less supported browser-specific features, which are usually not used. Check window.open in MDN for examples.
Let’s open a window with minimal set of features just to see which of them browser allows to disable:
Here most “window features” are disabled and window is positioned offscreen. Run it and see what really happens. Most browsers “fix” odd things like zero
width/height and offscreen
left/top. For instance, Chrome open such a window with full width/height, so that it occupies the full screen.
Let’s add normal positioning options and reasonable
Most browsers show the example above as required.
Rules for omitted settings:
- If there is no 3rd argument in the
opencall, or it is empty, then the default window parameters are used.
- If there is a string of params, but some yes/no features are omitted, then the omitted features are disabled, if the browser allows that. So if you specify params, make sure you explicitly set all required features to yes.
- If there is no
left/topin params, then the browser tries to open a new window near the last opened window.
- If there is no
width/height, then the new window will be the same size as the last opened.
open call returns a reference to the new window. It can be used to manipulate it’s properties, change location and even more.
In the example below, the contents of the new window is modified after loading.
Please note that external
document content is only accessible for windows from the same origin (the same protocol://domain:port).
For windows with URLs from another sites, we are able to change the location by assigning
newWindow.location=..., but we can’t read the location or access the content. That’s for user safety, so that an evil page can’t open a popup with
http://gmail.com and read the data. We’ll talk more about it later.
window.opener to access the window that opened it. It is
null for all windows except popups.
So both the main window and the popup have a reference to each other. They may modify each other freely assuming that they come from the same origin. If that’s not so, then there are still means to communicate, to be covered in the next chapter Cross-window communication.
If we don’t need a popup any more, we can call
newWindow.close() on it.
close() method is available for any
window.close() is ignored by most browsers if
window is not created with
true if the window is closed. That’s useful to check if the popup (or the main window) is still open or not. A user could close it, and our code should take that possibility into account.
This code loads and then closes the window:
Theoretically, there are
window.blur() methods to focus/unfocus on a window. Also there are
focus/blur events that allow to focus a window and catch the moment when the visitor switches elsewhere.
In the past evil pages abused those. For instance, look at this code:
When a user attempts to switch out of the window (
blur), it brings it back to focus. The intention is to “lock” the user within the
So, there are limitations that forbid the code like that. There are many limitations to protect the user from ads and evils pages. They depend on the browser.
For instance, a mobile browser usually ignores that call completely. Also focusing doesn’t work when a popup opens in a separate tab rather than a new window.
Still, there are some things that can be done.
- When we open a popup, it’s might be a good idea to run a
newWindow.focus()on it. Just in case, for some OS/browser combinations it ensures that the user is in the new window now.
- If we want to track when a visitor actually uses our web-app, we can track
window.onfocus/onblur. That allows us to suspend/resume in-page activities, animations etc. But please note that the
blurevent means that the visitor switched out from the window, but they still may observe it. The window is in the background, but still may be visible.
- A popup can be opened by the
open(url, name, params)call. It returns the reference to the newly opened window.
- By default, browsers block
opencalls from the code outside of user actions. Usually a notification appears, so that a user may allow them.
- The popup may access the opener window using the
window.openerproperty, so the two are connected.
- If the main window and the popup come from the same origin, they can freely read and modify each other. Otherwise, they can change location of each other and communicate using messages (to be covered).
- To close the popup: use
close()call. Also the user may close them (just like any other windows). The
blur()allow to focus/unfocus a window. Sometimes.
blurallow to track switching in and out of the window. But please note that a window may still be visible even in the background state, after
Also if we open a popup, a good practice is to notify the user about it. An icon with the opening window can help the visitor to survive the focus shift and keep both windows in mind.