[ 
https://issues.apache.org/jira/browse/WICKET-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599333#comment-13599333
 ] 

Jared Sol commented on WICKET-5071:
-----------------------------------

It appears that the request cycle ends up rendering the url by the call to 
renderUrl(Url url, IRequestHandler handler).

This method has a line String renderedUrl = getUrlRenderer().renderUrl(url);

The UrlRenderers renderUrlMethod then calls renderRelativeUrl(url).

This method has a line List<String> baseUrlSegments = getBaseUrl().getSegments()

The returned values between the outer and inner modal are different. The outer 
modal returns nothing [] while the inner modal returns [wicket, bookmarkable, 
com.qs.NestedModals.OuterModalContent]. I think this is what Martin was saying 
when the inner modal is calculated against the outer modal page. The segments 
in baseUrlSegments then get removed from the calculated url which strips the 
leading wicket/bookmarkable.
                
> 404 Error on Nested ModalWindows in IE7 and IE8
> -----------------------------------------------
>
>                 Key: WICKET-5071
>                 URL: https://issues.apache.org/jira/browse/WICKET-5071
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.5.8, 6.6.0
>         Environment: Internet Explorer 8.0.7601.17514
> Internet Explorer 7.0.5730.13
> Jetty 7 (multiple versions replicate the problem)
> Tomcat 6
>            Reporter: Jered Myers
>         Attachments: NestedModals.zip
>
>
> When opening a ModalWindow inside a ModalWindow, the inner ModalWindow 
> generates a 404 error.  Both windows use a PageCreator for content.
> To replicate, you must use an actual IE 7 or IE 8 browser, as this does not 
> replicate using developer tools and setting the document and brower to IE 7.
> The problem can be seen at 
> http://www.wicket-library.com/wicket-examples/ajax/modal-window.  I will 
> attach a Quickstart as well.

--
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

Reply via email to