> On Jun 28, 2023, at 8:23 AM, Ernesto Reinaldo Barreiro
> wrote:
>
> I think your question has been correctly answered already. But, anyways, it
> is pleasant to have questions in wicket's users list :-)
Indeed. Handled REALLY quickly! Next time I won’t wait so long to ask my dumb
> On Jun 28, 2023, at 8:27 AM, Bas Gooren wrote:
>
> Hi Shawn,
>
> That’s more of a styling issue.
>
> uses the “value” attribute to render the button text.
>
> For a you’ll need to put the value inside the button tag:
> value goes here
>
Ah yes, that’s it. Thank you Bas! For
This is true. Looking at the source code I don't why it needs to be a
button :-)
On Wed, Jun 28, 2023 at 4:34 PM Martin Grigorov
wrote:
> For me the real question is why is not supported too
> ?!
> IMO this is a bug!
>
> On Wed, Jun 28, 2023 at 4:28 PM Ernesto Reinaldo Barreiro <
>
I mean something like this:
;Wicket.Event.subscribe('/ajax/call/beforeSend', function(jqEvent,
attributes, jqXHR, errorThrown, textStatus) {
pageLoadingFrame("show");
});
Wicket.Event.subscribe('/ajax/call/failure', function(jqEvent, attributes,
jqXHR, errorThrown, textStatus) {
For me the real question is why is not supported too
?!
IMO this is a bug!
On Wed, Jun 28, 2023 at 4:28 PM Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> By the way... in almost all wicket applications I have worked with we had a
> blocking div covering the page and
By the way... in almost all wicket applications I have worked with we had a
blocking div covering the page and activated/deactivated via global AJAX
listeners.
On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney wrote:
>
> > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote:
> >
> > Hi Shawn,
> >
> >
Hi Shawn,
That’s more of a styling issue.
uses the “value” attribute to render the button text.
For a you’ll need to put the value inside the button tag:
value goes here
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 28 juni 2023 bij 15:24:44, Shawn McKinney (smckin...@symas.com)
You need to put something inside the button for it not to be tiny
On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney wrote:
>
> > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote:
> >
> > Hi Shawn,
> >
> > The code basically checks if you apply the behavior to a
> element.
> >
> > In other words:
>
> On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote:
>
> Hi Shawn,
>
> The code basically checks if you apply the behavior to a element.
>
> In other words:
>
> is considered an “invalid” element for this behavior.
>
> is considered “valid”.
>
Hello,
As part of my scientific ‘poke and
I think your question has been correctly answered already. But, anyways, it
is pleasant to have questions in wicket's users list :-)
On Wed, Jun 28, 2023 at 4:08 PM Shawn McKinney wrote:
> Howdy,
>
> I’m a little embarrassed to be asking. It seems so basic, should know it
> already.
>
> But,
Hi Shawn,
look at your markup and you will see, that the tag is not a
-tag, it's an -tag. If you change the markup the warning
disappears.
Dirk
Am 28.06.2023 um 15:07 schrieb Shawn McKinney:
Howdy,
I’m a little embarrassed to be asking. It seems so basic, should know it
already.
But,
Hi Shawn,
The code basically checks if you apply the behavior to a element.
In other words:
is considered an “invalid” element for this behavior.
is considered “valid”.
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 28 juni 2023 bij 15:08:52, Shawn McKinney (smckin...@symas.com)
Howdy,
I’m a little embarrassed to be asking. It seems so basic, should know it
already.
But, I’ve already spent a fair amount of time digging with no answers.
My usage of Ajax buttons generates this warning in the logs:
```
WARN - 28 Jun 2023 07:35:56,704 - IndicatingAjaxButton -
13 matches
Mail list logo
