JavaScript - Using the window.open method

​The syntax of the window.open method is given below:
window.open(URL, windowName[, windowFeatures])

URL
The URL of the page to open in the new window. This argument could be blank.

windowName
A name to be given to the new window. The name can be used to refer this window again.

windowFeatures
A string that determines the various window features to be included in the popup window (like status bar, address bar etc.)
The following code opens a new browser window with standard features.

window.open ("http://www.javascript-coder.com","mywindow")

 

Changing the features of the Popup

You can control the features of the popup using the last argument to the window.open method. The following code opens a window with a status bar and no extra features:

window.open ("http://www.javascript-coder.com","mywindow","status=1");

The code below opens a window with toolbar and status bar:

window.open ("http://www.javascript-coder.com", "mywindow","status=1,toolbar=1");

The table shows the features and the string tokens you can use:

status
The status bar at the bottom of the window.

toolbar
The standard browser toolbar, with buttons such as Back and Forward.

location
The Location entry field where you enter the URL.

menubar
The menu bar of the window

directories
The standard browser directory buttons, such as What’s New and What’s Cool

resizable
Allow/Disallow the user to resize the window.

scrollbars
Enable the scrollbars if the document is bigger than the window

height
Specifies the height of the window in pixels. (example: height=’350′)

width
Specifies the width of the window in pixels.

Examples

The following code opens a window with menu bar. The window is re-sizable and is having 350 pixels width and 250 pixels height.

window.open ("http://www.javascript-coder.com","mywindow","menubar=1,resizable=1,width=350,height=250");

A window with location bar, status bar, scroll bar and of size 100 X 100:

window.open ("http://www.javascript-coder.com", "mywindow","location=1,status=1,scrollbars=1, width=100,height=100");

 

Moving the window to a desired location

You can use the window.moveTo function to move the popup window to a desired location.

The code below shows positioning the popup at a desired location:

function mypopup()

{

mywindow = window.open("http://www.javascript-coder.com", "mywindow", "location=1,status=1,scrollbars=1, width=100,height=100");

mywindow.moveTo(0, 0);

}

The code positions the popup on the top left corner of the screen.

 

Putting it all together

Now we will combine all these information to create the popup windows of different types.
The Code below opens a popup window when you enter the page:

<html>

<head>

<title>JavaScript Popup Example 3</title>

</head>

<script type="text/javascript">

function poponload()

{

testwindow = window.open("", "mywindow", "location=1,status=1,scrollbars=1,width=100,height=100");

testwindow.moveTo(0, 0);

}

</script>

<body onload="javascript: poponload()">

<h1>JavaScript Popup Example 3</h1>

</body>

</html>

Notice that the URL is kept blank. This will open a blank window.

 

Popup On Exit

The following code pops up a window when the user exits a page.

<html>

<head>

<title>JavaScript Popup Example 3</title>

</head>

<script type="text/javascript">

function exitpop()

{

my_window = window.open("", "mywindow1", "status=1,width=350,height=150");

my_window.document.write('<h1>Popup Test!</h1>');

}

</script>

<body onunload="javascript: exitpop()" >

<h1>JavaScript Popup Example 4</h1>

</body>

</html>

The code contains an extra line:

my_window.document.write('<h1>Popup Test!</h1>')

This code displays a line ‘Popup Test!’ in the popup.

Comments

Post a Comment

Popular posts from this blog

SharePoint Designer 2013 Approval Workflow with Comments

Image
Adding Comments to a SharePoint 2013 Approval Workflow I needed the ability to capture comments from Approval Tasks in a workflow.  This has changed greatly in 2013 workflows.  Everything is more modular and as such must be built somewhat from scratch.
SharePoint 2013 workflows can become corrupt.  This may have been fixed by a patch, but please refer to a previous post before creating any 2013 workflows in Designer: http://www.ericjochens.com/2014/12/sharepoint-2013-workflow-observations.htmlSharePoint 2013 does not have a built-in approval workflow, nor does a built-in task item include comments.  I solved this by building my own approval workflow, and using a custom content type to include a comments field.A SharePoint 2013 Workflow will not store the Task ID when a task is created, so you cannot do a lookup into that task list to grab comments or any other field.  I solved this by creating a separate workflow in the task list to read the Related Items column, and update the origin…
Read more

Change SharePoint server hostname and Web Application Names

Note: I realize that many admins are reluctant to delete web applications.  I personally know why I ma doing it and how to achieve this easily.  You should always retain any customization you have added to the site, like web.config mods, etc.  The Alternate Access Mappings are always available, but they leave open holes that I do not wish to keep active.  I like a clean setup.
Why? Perhaps you need to clone a development, test, or some SharePoint server and you need to change the hostname so that it can exist on the same domain without a SID conflict.  Or you just have a use-case for wanting to rename the hostname of a SharePoint server.  It can be done, just make sure you go through all of the steps.

The Rename-SPServer PowerShell command can also be used to change the SQL Server name, for the case where you might move the databases to a new SQL server or instance and you need to point all of the farm servers to this new hostname\instance.

Changing the hostname isn't that bad, bu…
Read more

SharePoint Search - Content Processing Pipeline Failed to Process the Item

Image
SharePoint 2013 Search Crawls Stop Crawling All Content Recently the search system stopped successfully crawling content.  ASPX pages were crawled, but no content was being indexed. Opening up the crawl log showed thousands of errors with this message:
The content processing pipeline failed to process the item.  (Index was out of range.  Must be non-negative and less than the size of the collection.  Parameter name: index; SearchID = [GUID]) Note: the resolution is in the resolution section for those who cannot or refuse to read. What does this mean?  Honestly initially it made no sense.  So I learned a valuable lesson: I misguidedly spent the next 2 days trying the usual fixes like resetting the index, rebuilding the 2013 search components, and lastly what EVERYONE does: they fix it with a sledgehammer (in this case rebuilding the search service application).

But what if rebuilding the search service application is a horrible pain?  We have thousands of query rules, 30 result source…
Read more