This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes HTML, CSS and JavaScript and the fly likes window.opener performance error Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "window.opener performance error" Watch "window.opener performance error" New topic

window.opener performance error

James Ball

Joined: Apr 28, 2008
Posts: 1
I am working on a performance bug, where the user beats the refresh of the parent screen and opens a calendar popup. When the parent screen is refreshed, the calendar popup has a reference to the previous parent screen. When you click anywhere on the calendar popup, you receive an "Object doesn't support this property or method" error, which I expected to see if my logic is correct because when you click on the calendar it will write those changes to the parent window. Is there any way to force window.opener to utilize the current parent window? Are there ways to workaround this issue, without disabling the entire screen to ensure a button is not clicked prior to parent screen refresh?
Eric Pascarello

Joined: Nov 08, 2001
Posts: 15385
Is the refresh related to the pop up window opening? If so, why is that happening?

Bear Bibeault
Author and ninkuma

Joined: Jan 10, 2002
Posts: 63548

Most modern date pickers (and similar controls) will create the control elements on the same page by adding the new element to the current DOM (or revealing previously hidden elements). Opening a separate page in a child window will always incur this sort of problem. When the parent page goes away, the child is orphaned and opener is no longer valid. There is no way to cause opener to "hook up" to a new page.

[Asking smart questions] [About Bear] [Books by Bear]
I agree. Here's the link:
subject: window.opener performance error
It's not a secret anymore!