You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by "Richter, Marvin" <Ma...@freenetdigital.com> on 2014/11/03 14:46:32 UTC
Bug in wicket-bootstrap's Navbar
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
RE: Bug in wicket-bootstrap's Navbar
Posted by "Richter, Marvin" <Ma...@freenetdigital.com>.
Done https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/460
If you need more information please let me know.
-----Original Message-----
From: Martin Grigorov [mailto:mgrigorov@apache.org]
Sent: Monday, November 03, 2014 3:27 PM
To: users@wicket.apache.org
Subject: Re: Bug in wicket-bootstrap's Navbar
Create an issue at https://github.com/l0rdn1kk0n/wicket-bootstrap please
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Nov 3, 2014 at 4:22 PM, Richter, Marvin < Marvin.Richter@freenetdigital.com> wrote:
> 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: users@wicket.apache.org
> 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:mgrigorov@apache.org]
> Sent: Monday, November 03, 2014 2:55 PM
> To: users@wicket.apache.org
> 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 <
> Marvin.Richter@freenetdigital.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Bug in wicket-bootstrap's Navbar
Posted by Martin Grigorov <mg...@apache.org>.
Create an issue at https://github.com/l0rdn1kk0n/wicket-bootstrap please
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Nov 3, 2014 at 4:22 PM, Richter, Marvin <
Marvin.Richter@freenetdigital.com> wrote:
> 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: users@wicket.apache.org
> 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:mgrigorov@apache.org]
> Sent: Monday, November 03, 2014 2:55 PM
> To: users@wicket.apache.org
> 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 <
> Marvin.Richter@freenetdigital.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: Bug in wicket-bootstrap's Navbar
Posted by "Richter, Marvin" <Ma...@freenetdigital.com>.
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: users@wicket.apache.org
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:mgrigorov@apache.org]
Sent: Monday, November 03, 2014 2:55 PM
To: users@wicket.apache.org
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 < Marvin.Richter@freenetdigital.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug in wicket-bootstrap's Navbar
Posted by "Richter, Marvin" <Ma...@freenetdigital.com>.
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:mgrigorov@apache.org]
Sent: Monday, November 03, 2014 2:55 PM
To: users@wicket.apache.org
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 < Marvin.Richter@freenetdigital.com> 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
>
Re: Bug in wicket-bootstrap's Navbar
Posted by Martin Grigorov <mg...@apache.org>.
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 <
Marvin.Richter@freenetdigital.com> 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
>