Child window property window.opener null after postback

From: MrFez (MrFez_at_discussions.microsoft.com)
Date: 04/28/05

  • Next message: poifull: "Re: CryptProtectData failed when calling from ASP.NET" 
    Date: Wed, 27 Apr 2005 16:40:04 -0700

    I have an webform from which I open a child window to display a calendar.
    When a date is selected in the calendar window it attempts to set the value
    of a textbox in the main (parent) window by using the window.opener property
    to reference the textbox.

    Everything works fine initially. However if the the main window does a
    postback and the calendar is re-opened, its window.opener property will
    always be null.

    So: BEFORE main window executes a postback the calendar can be opened,
    close, and re-opened many times and window.opener is set properly.

    AFTER main window does a postback (another button was clicked) the calendar
    window can be opened but it cannot return a value because window.opener is
    always null.

    Note, this seems to be primarily a problem with Windows XP SP2 clients.
    Windows Server 2003 SP1 clients do not seem to have this problem.

    Any ideas?

  • Next message: poifull: "Re: CryptProtectData failed when calling from ASP.NET"