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 <smckin...@symas.com> wrote: > > > On Jun 28, 2023, at 8:11 AM, Bas Gooren <b...@iswd.nl> wrote: > > > > Hi Shawn, > > > > The code basically checks if you apply the behavior to a <button> > element. > > > > In other words: > > > > <input type=“button”> is considered an “invalid” element for this > behavior. > > > > <button> is considered “valid”. > > > > Hello, > > As part of my scientific ‘poke and hope’ methodology;-), I had tried that. > > Now, the warning has disappeared. But, the button renders on the page as a > tiny dot, that actually works. I doubt my users would be a big fan of it > (tiny buttons), although their eye doctors might? > > Anyway, all kidding aside, here’s what the html looks like: > > ``` > <button type=button class="ui-button ui-widget ui-state-default > ui-corner-all ui-button-text-only" > wicket:id="wspage1.button1" > value="wspage1.button1" name="wspage1.button1”/> > ``` > > Best > > — > Shawn > > > Met vriendelijke groet, > > Kind regards, > > > > Bas Gooren > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro