Support for opening pages in new tabs/windows breaks
RestartResponseAtInterceptPageException support
----------------------------------------------------------------------------------------------------
Key: WICKET-1255
URL: https://issues.apache.org/jira/browse/WICKET-1255
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.2.6
Reporter: Meetesh Karia
This is from an email I sent to the wicket users mailing list to which I
received no response:
{quote}
I'm running into a problem with the use of intercept pages together with wicket
1.2.x's support for opening pages in new tabs/windows. Basically, if someone
has a tab open to our site and then opens a link in another tab which causes
the user to be redirected to an intercept page, it will redirect one extra time
to create a new page map (that redirect happening through javascript).
Unfortunately, this causes wicket to lose track of the original destination of
the intercept, thus the intercept no longer works.
{quote}
As the pagemap for the new page is constructed without knowledge of the
continuation url, the new pagemap can't continue to the original destination.
That could be fixed when the page map is constructed in WebPage.PageMapChecker,
but I can't think of a way to know when to remove that continuation url from
the original page map.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.