Home/ Questions/Q 6006759
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T01:35:10+00:00

The ModalWindow does not work properly in Opera. Window content is not displayed but

  • 0

The ModalWindow does not work properly in Opera. Window content is not displayed but the browser’s error page is displayed The browser says “Internal communication error: Check that the address is spelled correctly, or try searching for the site.” an a text “http:///” is in the search bar of the error page.

Is there any solution available? I am using wicket 1.3.6.

Thanks and regards.

Edit: This is a screenshot from wicket example of the modal window error in opera 11. “Show modal dialog with a page” gave this error, but for “Show modal dialog with a panel” it’s working:

screenshot

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Look at this example and see it work in Opera. After that, look at the source code for the example and discover where you’re doing something different.

    Update:

    It appears there really is an issue in doing the “modal window with a page” in Opera, as I’ve now seen the same thing. I wasn’t on a machine with Opera yesterday but this morning I tried the example cited above and clicking on “Show modal dialog with a page” does indeed give the issue.

    Using Wicket Ajax Debug, I’m seeing a message “INFO: ReferenceError: Security error: attempted to read protected variable” after receiving the Ajax response.

    Searching the web for this message suggests it is tied in with the Opera security model dealing with cross-frame scripting. I see nothing specifically about Wicket, but there may be hints there.

    The “Show modal dialog with panel” doesn’t have this problem, so looking at that source may lead to a reasonable workaround.

    I can’t spend much time on it immediately, but I’ll continue looking, and let you know if I see the cause.

    Another Update

    This appears to be a known issue in Wicket 1.4, with a bug report. As we see in this discussion, it actually appeared earlier, but it may only be fixed in 1.5. The bug report may indicate a way to patch though.

    • 0