You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2018/09/05 12:28:00 UTC

[jira] [Resolved] (WICKET-6575) Ajax requests are still firing even when placeholder tag is written only

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

Sven Meier resolved WICKET-6575.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 9.0.0
                   8.1.0

When a component is invisible but writes a placeholder, it adds a new HTML attribute "data-wicket-placeholder"; this is then queried by wicket-ajax-jquery.js to prevent Ajax requests.

> Ajax requests are still firing even when placeholder tag is written only
> ------------------------------------------------------------------------
>
>                 Key: WICKET-6575
>                 URL: https://issues.apache.org/jira/browse/WICKET-6575
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 8.0.0
>            Reporter: Sven Meier
>            Assignee: Sven Meier
>            Priority: Minor
>             Fix For: 8.1.0, 9.0.0
>
>
> Wicket JavaScript has a default precondition, that prevents Ajax requests from being fired, should the component no longer be on the page.
> If a component is not visible, but nevertheless is writing a placeholder tag, the request is still fired. This results in a ListenerInvocationNotAllowedException and redirect to an access denied page.
> Wicket could add some magic to prevent this from happening.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)