Hi,
that setting is still used - it controls whether Ajax log messages end up in
the console at all.
Have fun
Sven
Am 7. April 2021 18:29:19 MESZ schrieb Bergmann Manfred
:
>Yep, that’s OK.
>
>But shouldn’t the settings also be gone?
>
>
>
>Manfred
>
>
>> Am 07.04.2021 um 17:32 schrieb Sven M
Yep, that’s OK.
But shouldn’t the settings also be gone?
Manfred
> Am 07.04.2021 um 17:32 schrieb Sven Meier :
>
> Yes, it was deemed superfluous:
>
> https://issues.apache.org/jira/browse/WICKET-6667
>
> Use you favorite browser's JS console instead.
>
> Best regards
> Sven
>
>
> O
Yes, it was deemed superfluous:
https://issues.apache.org/jira/browse/WICKET-6667
Use you favorite browser's JS console instead.
Best regards
Sven
On 07.04.21 16:15, Ernesto Reinaldo Barreiro wrote:
It is gone there AFAIK.
On Wed, Apr 7, 2021 at 5:11 PM Bergmann Manfred
wrote:
Hi.
E
It is gone there AFAIK.
On Wed, Apr 7, 2021 at 5:11 PM Bergmann Manfred
wrote:
> Hi.
>
> Even when setting explicitly:
>
> getDebugSettings().setAjaxDebugModeEnabled(true)
>
> I don’t see the Ajax debug window.
> Was this a change in Wicket 9?
>
>
> Manfred
>
>
>
Hi.
Even when setting explicitly:
getDebugSettings().setAjaxDebugModeEnabled(true)
I don’t see the Ajax debug window.
Was this a change in Wicket 9?
Manfred
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For a
