Databases
StackOverflow2013
Postsdbo
POSharing Variables Between Colorbox(s) Loading different pages - Where does the return variable go?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSharing Variables Between Colorbox(s) Loading different pages - Where does the return variable go?
    text
    copied!<p>I have a page with a link that opens a standard colorbox window(1) which is a record summary. On the page displayed inside of colorbox, I have several more links that will open selection pages where a user can pick a person or a status and save it back to the summary form. These links are also designed to open in the colorbox window(2), here is the function: </p> <pre><code> function makeColorboxMES(mes) { if (mes == 'changeLog') { href = '/RootDirectory/MyReport/ChangeLog.aspx; } if(mes == 'employeeByName') { href = '/RootDirectory/MyReport/EmployeeByName.aspx?Val=Name; } if (mes == 'getStatus') { href = '/RootDirectory/MyReport/SelectStatus.aspx?Val=Status; } parent.$.fn.colorbox({ iframe: true, href: href, width: '70%', height: '70%', escKey: true, inline: false, showClose: true, overlayClose: false, onLoad: function () { $('#cboxClose').hide() } }); } </code></pre> <p>After the user has made their selection, there is a javascript function on the master page that is supposed to capture their choice, it looks like this: </p> <pre><code> function restartList() { if (Val == 'Status') { $('[id$=status]').val(Codename); $('[id$=hidStatus]').val(CodeNumber); } } </code></pre> <p>The selection page itself is working correctly and sending out the variable but the master page javascript function never fires. I believed that this was because the original colorbox window is still open. So I tried moving the code to the actual remaining colorbox page that's still open but that doesn't fire either. Can someone help me understand exactly where in the DOM my data is being returned to? </p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload