Usage of window.location.href (dynamic output jump)_Basic knowledge

location.href in JavaScript has many uses, mainly as follows.

self.location.href="/url" The current page opens the URL page
location.href="/url" The current page opens the URL page
windows.location.href="/url" The current page opens the URL page. The first three usages are the same.
this.location.href="/url" The current page opens the URL page
parent.location.href="/url" Open a new page on the parent page
top.location.href="/url" Open a new page on the top page

If the frame is customized on the page, you can replace the parent self top with the name of the customized frame. The effect is to open the url address in the frame window

In addition, window.location.href=window.location.href; and window.location.Reload() both refresh the current page. The difference lies in whether data is submitted. When data is submitted, window.location.Reload() will prompt whether to submit it. window.location.href=window.location.href; will submit the data to the specified url

When writing ASP.Net programs, we often encounter the problem of page jumps. We often use Response.Redirect to jump to ASP.NET frame pages. If the customer wants to use prompts when jumping, this is It doesn’t work anymore, such as:

Copy code The code is as follows:

Response.Write("< script>alert('Congratulations, your registration is successful!');< /script>");
Response.Redirect("main.html");

At this time, our prompt content will jump before it comes out, which is no different from Response.Redirect("main.html");.

At this time we use the following code to test it:

Another implementation of ASP.NET framework page jump

Copy code The code is as follows:

Response.Write("< script language=javascript>alert('Congratulations, your registration is successful!')< /script>");
Response.Write("< script language=javascript>window.location.href='main.html'< /script>");

This meets our requirements. After the prompt, the page will jump.

The most important thing is that the window.location.href statement can realize that the page of one frame refreshes the page of another frame after executing the server-side code (Response.Redirect cannot achieve this, at least I have not found it):

For example: There are two frames in the index.htm page, namely frameLeft and frameRight. After executing the server-side code in the frameRight page, refresh the page in frameLeft.

The most common thing before was to automatically refresh the login box after registration, so that the login box is replaced by the logged-in page. As long as you add a paragraph after the successful registration code, you can refresh the page of another frame. The code is as follows:

Copy code The code is as follows:

Response.Write("< script language=javascript>alert('Congratulations, your registration is successful!')< /script>");
Response.Write("< script language=javascript>window.parent.frameLeft.location.href='main.html'< /script>");

This solves the problem of ASP.NET frame page jump interruption. In fact, this method is generally used in asp and php.

"window.location.href", "location.href" is the jump to this page
"parent.location.href" is a page jump to the previous level
"top.location.href" is the outermost page jump

Example:

If A, B, C, and D are all jsp, D is the iframe of C, C is the iframe of B, and B is the iframe of A, if the js in D is written like this

"window.location.href", "location.href": D page jump
"parent.location.href": C page jump
"top.location.href": A page jump

If there is a form in page D,

: The D page jumps after the form is submitted
: A new page pops up after the form is submitted
: C page jumps after the form is submitted
: Page A jumps after the form is submitted

Regarding page refresh, the D page says:

"parent.location.reload();": C page refresh (of course, you can also use the opener object of the child window to obtain the object of the parent window: window.opener.document.location.reload(); )

"top.location.reload();": A page refresh