Wicket interaction between wicket-applications on localhost
<p>I'm experiencing abnormal behaviour in ajax-related clicks in two Wicket Applications that both run on the same <code>localhost</code> on different ports (both served by <code>Jetty</code>)</p>

<p>I have two applications open in two tabs in Chrome. When I click on an <code>AjaxLink</code> in one of the applications, it sometimes works and sometimes does nothing (or something in the other Wicket tabs, as I see the tab title doing something).</p>

<p>This leads to undesired behaviour, as the links no longer work as required.</p>

<p>What can I do to prevent this interaction between tabs?</p>