[jira] Commented: (WICKET-1231) Fast multiple clicks on Link bound on non- element causes error.

["Johan Compagner (JIRA)" <ji...@apache.org>]

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

Johan Compagner commented on WICKET-1231:
-----------------------------------------

How do you double click?
Do you wait first for the page to be loaded?
Else you would click on the exact same url and that url is something like: "wicket:interface=xxxxx"

You say you fast click. So i guess you dont wait, and the only thing you do is set a next page. 
That should just be done just twice. You don't rerender the same page after the click so that page is not changed
somehow so the second link click should just find the page again.
So i don't see what can go wrong in your situation please attach a quickstart app to this issue.


> Fast multiple clicks on Link bound on non-<A> element causes error.
> -------------------------------------------------------------------
>
>                 Key: WICKET-1231
>                 URL: https://issues.apache.org/jira/browse/WICKET-1231
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-rc2
>         Environment: Tomcat 6, Firefox 2.0.0.11, Linux
>            Reporter: Mika Salminen
>            Priority: Minor
>
> When you attach a link component to some other element that <A>, fast clicking on the element causes usually errors.
> This issue can be demonstrated for example by creating link on table cell with html code:
> ...
> <tr>
> 	<td wicket:id="alink"
> 	style="width: 100px; height: 100px; background-color: red;">alink</td>
> </tr>
> ...
> and Java code:
> ...
> add(new Link("alink") {
> 	public void onClick() {
> 		setResponsePage(TestPage.class);
> 	};
> });
> ...
> Now if you for example double-click the link you will probably get HTTP 404 or some other error.
> I think that the problem is caused by the onclick event processing and relative urls.
> For example by double-clicking a link, two onclick events are fired. First event sets the window.location.href to correct address appending the relative url "ExamplePage/param1/val1" to current url. Second event appends the "ExamplePage/param1/val1" again and now the resultant address is incorrect "ExamplePage/param1/val1/ExamplePage/param1/val1".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.