Ah no. It's because of this:
@Override
protected void onInitialize() {
super.onInitialize();
this.setRenderBodyOnly(true);
}
In the NavbarDropDownButton.
-----Original Message-----
From: Richter, Marvin
Sent: Monday, November 03, 2014 3:21 PM
To: [email protected]
Subject: RE: Bug in wicket-bootstrap's Navbar
That's the thing, I couldn't find a solution that seems to be the right way to
fix it.
My dirty workaround is to override the newIntitializerScript function and just
remove the 'this'.
Because applying setOutputMarkupId(true) doesn't have the expected effect,
neither on the ListView nor the Component itself. I think that is because of
the wicket:enclosure.
-----Original Message-----
From: Martin Grigorov [mailto:[email protected]]
Sent: Monday, November 03, 2014 2:55 PM
To: [email protected]
Subject: Re: Bug in wicket-bootstrap's Navbar
Hi,
Thanks for reporting!
Do you have a GitHub account ? Send us a Pull Request please !
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Nov 3, 2014 at 3:46 PM, Richter, Marvin <
[email protected]> wrote:
> Hi Martin & Michael,
>
> There is a bug in the Navbar Component which causes
> NavbarDropDownButtons to not work.
>
> DropDownButton's newInitializerScript function uses 'this' so in the
> header it renders: $('#component2 .dropdown-toggle').dropdown();
>
> But the Navbar component does not call setOutputMarkupId(true) on the
> components contained in the alignedComponentListViews.
>
> Best,
> Marvin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
