IMO all kinds of "how to prevent user-action-xyz" aproaches are flawed
and bad design.
The "middle-mouse-button" is just one of several methods to open links
in a new tab/window. E.g. in most browsers you can archive this via
right-click, holding STRG or Command-Key or Plugin or...
So your best choice would be to have some kind of "onclick" action and a
dummy-link that only shows some kind of "sorry this action requires JS"
that is opend then.
Alternativly for links you can simply set the target to "#" or something.
Am 26.03.2015 10:07, schrieb Patrick Davids:
Hi Martin,
I missed something.
We have a kind of own LinkComponent class here and someone in our team
implemented an AjaxFallbackLink in the upper class hierarhcy, so
currently we have a AjaxFallbackLink case here.
I didnt know that.
Thats the reason why I have a null AjaxRequestTarget.
Sorry, for giving a wrong hint here...
I removed the AjaxFallbackLink.
Now, the browser opens a new tab, with just having "javascript:;" as url.
(This also avoids the NPE issue mentioned in my previous mail.)
So, my question is reducing now to (and is not really wicket related
anymore):
What the best practise to prevent a middle mouse click?
best regards
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
