yes -igor
On Sun, Apr 19, 2009 at 1:54 AM, Live Nono <[email protected]> wrote: > hi > > In case some one is interested, i found the solution : adding > getPageSettings().setAutomaticMultiWindowSupport(true); solves the > issue. > > I'm quite surprised though because the javadocs of this setting says > it's enabled by default, which doesn't seem to be the case in fact. > Should I open a jira issue for this ? > > bye > nono > > > > > 2009/4/18 Live Nono <[email protected]>: >> Hi >> >> I've just spotted the same behavior within the wicket examples page >> itself, there : >> http://www.wicket-library.com/wicket-examples/ajax/tree/simple.1 >> >> Open two tabs/windows of the same browser and then play with the tree >> in one page and then the others, then it'll fail "internal error" it >> says... >> >> In fact the state of the tree seems to be shared among the two pages : >> do some changes on one page and then refresh the other page (with F5), >> it'll have the state of the previous one. >> >> Is it an expected behavior for you ? If so, could someone tell me why >> and if it's possible to avoid it ? >> >> thanks in advance >> nono >> >> 2009/4/17, Live Nono <[email protected]>: >>> Hi >>> >>> I'm still working on this tree need and I've discovered this issue : >>> - opening the page tree in Firefox (or Iceweasel in my ubuntu) >>> - navigating the tree >>> - opening the page tree in another tab or instance of firefox >>> - navigating the tree in this second instance >>> - when willing again to navigate in the first page, it breaks with an >>> Unexpected RuntimeException >>> >>> However, browsing in 2 different browsers at the same time isn't an >>> issue (at least with Iceweasel and epiphany, the gnome web browser). >>> When using 2 epiphany (tabs or instances) at the same time, the issue >>> is the same. >>> >>> My detailed config is Mozilla/5.0 (X11; U; Linux i686; en-US; >>> rv:1.9.0.7) Gecko/2009032803 Iceweasel/3.0.6 (Debian-3.0.6-1) with >>> iceweasel 3.0.6 and epiphany/gnome web browser 2.22.3 >>> >>> The page in question is heavy on the Ajax side, so perhaps it isn't >>> directly TreeLink related. >>> >>> Am I missing something or... ? >>> >>> Thanks in advance >>> nono >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
