You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2007/12/19 22:57:43 UTC

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

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

Johan Compagner reassigned WICKET-1231:
---------------------------------------

    Assignee: Matej Knopp

just checked in a fix that seems to work for FF and IE
Matej is checking some more.

> 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
>            Assignee: Matej Knopp
>            Priority: Minor
>         Attachments: testapp-src.zip, TestApp.war
>
>
> 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.