This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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?
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.