The first window's name is determined in WebPage.PageMapChecker, and cannot
be changed there. I'd probably just call
PopupSettings#setWindowName("wicket-wicket:default") whenever the pagemap
name is null. In lieue of a wicket-core patch, a custom PopupSettings
subclass that does this automatically would probably be helpful.On Thu, Sep 8, 2011 at 4:28 PM, Jered Myers <[email protected]>wrote: > Do you know where I can set the window name of the first window? I can use > JavaScript to reset it, but I am not sure if this will mess up the PageMap > process. > > > On 9/8/2011 4:12 PM, Dan Retzlaff wrote: > >> Check out PopupSettings#**getPopupJavaScript(). If the pagemap name is >> null it >> uses "". Since you've enabled AutomaticMultiWindowSupport, you know it >> should be "wicket-wicket:default". >> >> You might consider submitting a JIRA to suggest that this function use "" >> or >> "wicket-wicket:default" based >> on Application.get().**getPageSettings().**getAutomaticMultiWindowSupport >> **(). >> That way other users won't encounter this gotcha. >> >> On Thu, Sep 8, 2011 at 3:47 PM, Jered Myers<jeredm@** >> maplewoodsoftware.com <[email protected]>>wrote: >> >> It appears the initial window name is "wicket-wicket:default". The other >>> tab windows match the PageMap name. Thanks for the help! I will explore >>> a >>> way to manipulate the window name. >>> >>> >>> On 9/8/2011 3:16 PM, Dan Retzlaff wrote: >>> >>> In step #5, what page map name do you use in your popup settings? Does >>>> it >>>> match the window.name global variable in that tab? (Use a browser >>>> debugger >>>> to check.) If yes, that should do the trick by my reading of the code. >>>> >>>> On Thu, Sep 8, 2011 at 2:19 PM, Jered Myers<jeredm@** >>>> maplewoodsoftware.com<jeredm@**maplewoodsoftware.com<[email protected]> >>>> >>wrote: >>>> >>>> >>>> I'm using Wicket 1.4.18. >>>> >>>>> I'm having trouble moving between browser tabs in my application as I >>>>> am >>>>> opening a duplicate tab. Here is an example: >>>>> 1. The user starts on browser tab A via a mounted page (e.g. >>>>> www.mysite.com/MyApp/PageA) >>>>> 2. The user clicks on a bookmarkable link (with popup settings >>>>> including >>>>> a >>>>> PageMap name) to browser tab B. The new browser tab opens correctly. >>>>> 3. The user clicks on a bookmarkable link (with popup settings >>>>> including >>>>> a >>>>> PageMap name) to browser tab C. The new browser tab opens correctly. >>>>> 4. The user clicks on a bookmarkable link (with popup settings >>>>> including >>>>> a >>>>> PageMap name) to browser tab B. The browser tab for B is already open, >>>>> so >>>>> the user switches back to browser tab B. >>>>> 5. The user clicks on a bookmarkable link (with popup settings >>>>> including >>>>> a >>>>> PageMap name) to browser tab A. A new browser tab A opens when I want >>>>> the >>>>> user to be returned to the already open tab A. >>>>> >>>>> Here is my mounting procedure: >>>>> mount(new QueryStringUrlCodingStrategey(******"PageA", PageA.class); >>>>> >>>>> Also, AutomaticMultiWindowSupport is on. >>>>> >>>>> -- >>>>> Jered >>>>> >>>>> >>>>> ------------------------------******--------------------------**--** >>>>> --**--------- >>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.****apa**che.org< >>>>> http://apache.org**> >>>>> <users-unsubscribe@**wicket.**apache.org <http://wicket.apache.org>< >>>>> users-unsubscribe@**wicket.apache.org<[email protected]> >>>>> > >>>>> >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>>> ------------------------------****----------------------------** >>> --**--------- >>> To unsubscribe, e-mail: >>> users-unsubscribe@wicket.**apa**che.org<http://apache.org> >>> <users-unsubscribe@**wicket.apache.org<[email protected]> >>> > >>> For additional commands, e-mail: [email protected] >>> >>> >>> > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
