jst and robert and I discussed this on IRC earlier. An easy workaround would be to have the reporter code use an onload listener to call initPrivacyNotice() for the first panel, rather than relying on the "onpageshow" pseudo-event that's fired from the wizard constructor.
That wouldn't fix other wizards that might also have this bug, though. I don't see a clean way to fix this in a generic way, since the dialog code can't tell whether or not the document is loaded yet (so it can't reliably defer calling event handlers until onload).
jst and robert and I discussed this on IRC earlier. An easy workaround would be to have the reporter code use an onload listener to call initPrivacyNotice() for the first panel, rather than relying on the "onpageshow" pseudo-event that's fired from the wizard constructor.
That wouldn't fix other wizards that might also have this bug, though. I don't see a clean way to fix this in a generic way, since the dialog code can't tell whether or not the document is loaded yet (so it can't reliably defer calling event handlers until onload).