Major browsers have popup blockers which sometimes prevent sites to open new tabs. This article investigates how popup blockers currently works, what they block and how to overcome problems caused by them.
First chapter gives short overview of popup blockers. The rest of article shows multiple ways how to open new tab and how to work around browsers limitations.
Popup Blockers
For the browser, there is no difference between new tab and popup. Popup blockers treats them the same way. Therefore, this article uses “new tab” and “new window” interchangeably.
Popup blocker built inside the Firefox is willing to open new tab only from onclick hander. It prevents tab opening from mouse over event, network request response, and from inside script in the body. Instead of opening new tab, firefox will show yellow warning banner which says Firefox prevented this site from opening popup. It is possible to turn off the warning, but that requires user action.
Edge works similarly to Firefox, except that banner is white and show on bottom of the window.
Chrome always prevents new tabs from network request response. It mostly prevents also new tabs from on mouse over event and script inside the body. The last two are sometimes created, but I did not found when exactly. Chrome shows small icon in url bar when it refuses to open the new tab. User can click on it and allow popups manually.
Html Link
The easiest way to create a link that opens in a new tab is to add target="_blank" to it. It works in Chrome, Firefox and Edge.
<a href="http://gooogle.com" target="_blank">Normal Link</a>
This is how it renders: Normal Link
JavaScript
JavaScript can open new tab using the window.open(URL, name, specs, replace) function. The trick is to put '_blank' into name argument.
window.open('https://www.google.com', '_blank');
This works in most, but not all, situations. Most importantly, Edge and Firefox block new tab from network request response handler. When the url have to be loaded from backend, Firefox requires tricks to work.
This chapter has two sections. First section deals with situation when the frontend knows the url. Second section shows how to open link in new tab when the fronted needs to send network request.
When the Url is Known
In this chapter, we will try to open a new tab from mouse click, from timer, from mouse over and from a script inside the body.
From Click
Open new tab from onclick attribute of html tag works from Chrome, Firefox and Edge:
<a href="#" onclick="
window.open('https://www.google.com', '_blank');
return false;
">on click</a>
This is how it renders: on click
From Timer Inside Click
You can also start a timer while handling users onclick method and open a new tab later from the timer. It works in Chrome, Firefox and Edge:
<a href="#" onclick="
setTimeout(() => window.open('https://www.google.com', '_blank'), 500);
return false;
">click starts timer</a>
This is how it renders: click starts timer
From Mouse Over
Open new tab from onmouseover attribute of an html tag does not work. Firefox and Edge block it all the time. Chrome blocks it most of the time, although blocking is not perfect and the tab occasionally shows up:
<a href="#" onmouseover="
window.open('https://www.google.com', '_blank');
return false;
">on mouse over</a>
This is how it renders: on mouse over
From Timer Inside Mouse Over
Open new tab from timer started inside onmouseover does not work. Firefox and Edge block it all the time. Chrome blocks it most of the time, although blocking is not perfect and the tab shows up once in a while:
<a href="#" onmouseover="
setTimeout(function() {
window.open('https://www.google.com', '_blank');
} ,500);
return false;
">timer on mouseover</a></br>
This is how it renders: timer on mouseover
From Body Onload
Opening new tab from script in body is blocked by all three browser. Add this inside the body tag to see it:
<script>
console.log("installing");
setTimeout(function() {
console.log("running");
window.open('https://www.google.com', '_blank');
}, 500);
</script>
Fetching Url From Backend
More interesting and useful case is when the web application needs to fetch the url from backend. The straightforward solution does not work, Edge and Firefox block the new tab. However, this use case is too useful to be ignored, so we will build workaround.
From Request Response
Opening new tab from request response works only in Chrome. Edge and Firefox shows yellow warning and prevents new tab to open:
<script>
function fromHttpRequest() {
const Http = new XMLHttpRequest();
const url='https://jsonplaceholder.typicode.com/posts';
Http.open("GET", url);
Http.send();
Http.onreadystatechange = (e) => {
console.log(Http.responseText)
window.open('https://www.google.com', '_blank');
}
}
</script>
<a href="#" onclick="
fromHttpRequest();
return false;
">from http request</a></br>
This is how it renders: from http request
Starting timer from request response does not help. Chrome and Edge will open the tab, but Firefox will show warning instead. I have omitted the example, because it is long and almost the same as timers above.
Workaround 1
The workaround is to combine javascript interval started from user click, network request and let them communicate through variable.
- Network request waits for response. Then it sets the common variable.
- The interval periodically checks variable value. It opens new tab once the variable has the response. Then the interval removes itself.
<script>
function intervalListensForRequestResponse() {
var iHaveTheResponse; // shared variable
// send request
const Http = new XMLHttpRequest();
const url='https://jsonplaceholder.typicode.com/posts';
Http.open("GET", url);
Http.send();
Http.onreadystatechange = (e) => {
console.log(Http.responseText)
iHaveTheResponse = 'https://www.google.com';
}
// periodically check the variable
var refreshIntervalId = setInterval(function(){
console.log('tick ' + iHaveTheResponse);
if (iHaveTheResponse) {
window.open(iHaveTheResponse, '_blank')
clearInterval(refreshIntervalId);
}
}, 500);
return false;
}
</script>
<a href="#" onclick="
return intervalListensForRequestResponse();
">interval listens for request response</a>
This is how it renders: interval listens for request response
Workaround 2
If the frontend knows for sure it will have to open new tab and just needs to acquire correct url from backend, you can:
- Open new window and keep reference to it.
- Send the request.
- Set url to newly opened window.
The disadvantage of this solution is that new window is opened before the response from backend came back. There is a blank window for few miliseconds. In addition, it is impossible to make backend decide whether the window will be needed or not.
<script>
function startByOpeningTheWindow() {
var newTab = window.open("", '_blank');
if (newTab==null) {
return ;
}
// send request
const Http = new XMLHttpRequest();
const url='https://jsonplaceholder.typicode.com/posts';
Http.open("GET", url);
Http.send();
Http.onreadystatechange = (e) => {
console.log(Http.responseText);
newTab.location.href = 'https://www.google.com';
}
return false;
}
</script>
<a href="#"
onclick="startByOpeningTheWindow();"
>first open the window, change url later</a></br>
This is how it renders: first open the window, change url later
Few Notes on Open Function
Communication between original window and new tab is possible if they have the same origin. If they show pages from different domains, the communication is blocked by the browser due to Same Origin Policy rules. It ends with Error: uncaught exception: Permission denied to get property error.
The window.open function returns reference to the tab that was just opened. The original page can use it to call functions inside newly opened tab. If the Firefox popup blocker blocked the popup, the function returns null. You can use this to check whether the new tab was blocked. This method works only for built-in popup blocker, it does not work for ad-blocking addons.
New tab has the opener property which can be used to call functions inside the main window. It also has the closed property. Main window can use it to check whether the child tab was open or not.
All Examples
All tested cases are on this page.
Published on Java Code Geeks with permission by Maria Jurcovicova, partner at our WCG program. See the original article here: Open Link in New Tab Opinions expressed by Web Code Geeks contributors are their own. |
In ‘workaround 2’, you have a blank window / tab whilst the request is being handled. You can improve that by pre-writing to the new window e.g. after your
if (newTab == null ) return;
put something like …
newtab.document.open();
newtab.documen.write(‘Working …. Please wait …’);
newtab.document.close();