[
https://issues.apache.org/jira/browse/WICKET-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639412#comment-13639412
]
Uffe Heerfordt commented on WICKET-5119:
----------------------------------------
Hi,
The first proposed solution wasen't very thought through by me - I have
afterwards attempted different solutions like doing an explict close() on the
popup... attempting to to store the window in a global variable to reuse it...
and doing a document write... to get IE to unload the plugin. However none of
the attempts fully worked, I guess the two options are to either remove the
focus logic or to supress the exception by adding try{}catch(ignore){} around
the statement.. When testing in IE without the logic, it seems to auto focus
the popup automaticly. There dosen't seem to be a perfect fix for this atm,
only a workaround.
Br,
Uffe
> PopupSettings IE8 - dosen't work secound time a link is clicked.
> ----------------------------------------------------------------
>
> Key: WICKET-5119
> URL: https://issues.apache.org/jira/browse/WICKET-5119
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.4.0
> Reporter: Uffe Heerfordt
> Assignee: Martin Grigorov
> Attachments: pages-in-popup.tgz, quickstart-onissue.zip
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> Hi,
> The popup functionality causes a script error in IE8, if the popup window is
> already open. As a result the link's default behaviour is executed instead -
> as ' return false; ' never is reached.
> Class: org.apache.wicket.markup.html.link.PopupSettings
> The problem exists in line: 188 // if(w.blur) w.focus();
> In IE8 blur and focus isen't defined - secound time a popup link is called
> and therefore the logic breaks.
> //An alternative: (test if w.blur is defined)
> script.append("'); if( jQuery.isFunction( w.blur ) && w.blur ) { w.focus(); }
> ").append(" return false;");
> Br,
> Uffe.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
