Re: Possible bug / edge case found where page is not detached

Now that is a stellar bug report. From: Bas Gooren Sent: Sunday, July 25, 2021 12:06 AM To: users@wicket.apache.org ; Sven Meier Subject: Re: Possible bug / edge case found where page is not detached Hi Sven, Done - https://issues.apache.org/jira/browse/WICKET

Re: Possible bug / edge case found where page is not detached

Hi Sven, Done - https://issues.apache.org/jira/browse/WICKET-6908 Met vriendelijke groet, Kind regards, Bas Gooren Op 24 juli 2021 bij 10:29:38, Sven Meier (s...@meiers.net) schreef: Hi Bas, that sounds like a bug. Your quickstart didn't make it through the mailing list, would you please

Re: Possible bug / edge case found where page is not detached

Hi Bas, that sounds like a bug. Your quickstart didn't make it through the mailing list, would you please attach it to a new Jira issue? Thanks Sven Am 23. Juli 2021 19:30:46 MESZ schrieb Bas Gooren : >Hi all, > >Today I spent the better part of my day investigating a bug report &

Possible bug / edge case found where page is not detached

Hi all, Today I spent the better part of my day investigating a bug report regarding a hibernate LazyInitializationException. Since we use detaching models everywhere and (in general) never see such issues anymore, this one was interesting :-) After much debugging I found out what is happening

Re: Bug with backbutton in Chrome / Edge

all, > > FYI: we found a bug in Chrome that mainly affects Wicket applications > when navigating back. > > https://bugs.chromium.org/p/chromium/issues/detail?id=1225212 > > It is easily reproducable with the

Bug with backbutton in Chrome / Edge

Hello all, FYI: we found a bug in Chrome that mainly affects Wicket applications when navigating back. https://bugs.chromium.org/p/chromium/issues/detail?id=1225212 It is easily reproducable with the quickstart in the ticket

Re: Bug in AnnotProxyFieldValueFactory::getBeanName

* > * @param field > * @return bean name > */ > private String getBeanName(final Field field, String name, boolean > required, Class generic) > { > if (Strings.isEmpty(name)) > { > Class fieldType = field.getType(); > SimpleEntry, Class> ke

Bug in AnnotProxyFieldValueFactory::getBeanName

getBeanName(final Field field, String name, boolean required, Class generic) { if (Strings.isEmpty(name)) { Class fieldType = field.getType(); SimpleEntry, Class> keyPair = new SimpleEntry, Class>(fieldType, generic); name = beanNameCache.get(fieldType); // BUG HERE, must be k

Re: Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi Conny, Actually the javadoc is already there - see IComponentInheritedModels's javadoc. We cannot copy/paste it at each and every component implementation. It is something specific to this IModel impl, not the components.

Re: Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi Conny, If you create a PR with Java doc improvements I'm sure committers will be happy to merge it :-) On Wed, Dec 20, 2017 at 8:24 AM, Conny Kühne wrote: > Hi Sven, > > thanks. Maybe the javadoc of the tree classes should state this. It is not > obvious, e.g., why

Re: Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

ow whether this is a bug so I'll ask here first. In the wicket tree examples, when I get a WicketRuntimeException in the org.apache.wicket.examples.tree.BeginnersTreePage when I set a model to the page as follows: public BeginnersTreePage() { setDefaultModel(new CompoundProperty

Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi, don't know whether this is a bug so I'll ask here first. In the wicket tree examples, when I get a WicketRuntimeException in the org.apache.wicket.examples.tree.BeginnersTreePage when I set a model to the page as follows: public BeginnersTreePage() { setDefaultModel(new

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

nce is no joking mantter =) > > > > 2017-12-13 3:56 GMT+02:00 Lon Varscsak <lon.varsc...@gmail.com>: > > > Haha, sure…I was sure someone was going to argue with me. :P > > > > > > -Lon > > > > > > On Tue, Dec 12, 2017 at 6:23 PM, Mar

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

t; > -Lon > > > > On Tue, Dec 12, 2017 at 6:23 PM, Martin Makundi < > > > > martin.maku...@koodaripalvelut.com> wrote: > > > Good find! Sounds like a bug, file to jira? > > > > > > 2017-12-12 23:38 GMT+02:00 Lon Varscsak <lon

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

hat happens. Please file a bug report and we'll look into it Martijn On Tue, Dec 12, 2017 at 10:38 PM, Lon Varscsak <lon.varsc...@gmail.com> wrote: > Okay, so here's the situation, I have a component where an Ajax request > displays a large table (1000ish rows). It display f

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

wrote: > > > Good find! Sounds like a bug, file to jira? > > > > 2017-12-12 23:38 GMT+02:00 Lon Varscsak <lon.varsc...@gmail.com>: > > > > > Okay, so here's the situation, I have a component where an Ajax request > > > displays a large table (1000

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

Haha, sure…I was sure someone was going to argue with me. :P -Lon On Tue, Dec 12, 2017 at 6:23 PM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote: > Good find! Sounds like a bug, file to jira? > > 2017-12-12 23:38 GMT+02:00 Lon Varscsak <lon.varsc...@gmail.co

Re: Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

Good find! Sounds like a bug, file to jira? 2017-12-12 23:38 GMT+02:00 Lon Varscsak <lon.varsc...@gmail.com>: > Okay, so here's the situation, I have a component where an Ajax request > displays a large table (1000ish rows). It display fast, no problem, not a > great u

Performance issue (possible bug since 7.2.0…up to and including 8.0.0-M8)

Okay, so here's the situation, I have a component where an Ajax request displays a large table (1000ish rows). It display fast, no problem, not a great use of resources (not paginating), but ignore that for now. I then have another Ajax request where I tell the wicket component to not be visible

Re: WiQuery 6.x and JQuery UI draggable (auto-scroll) bug

Best regards, Sebastien. On Tue, Nov 14, 2017 at 2:08 PM, Rakesh A <iamrakes...@rediffmail.com> wrote: > Hi, > > We are using wiquery 6.13.0 to build some interactive UI. This includes > JQuery's UI draggable, droppable, etc. > jquery-ui-1.10.4 is used in wiquery-6.13.

WiQuery 6.x and JQuery UI draggable (auto-scroll) bug

Hi, We are using wiquery 6.13.0 to build some interactive UI. This includes JQuery's UI draggable, droppable, etc. jquery-ui-1.10.4 is used in wiquery-6.13.0 There was a bug with jquiery-ui in draggable component. The auto-scroll does not work properly, which can be seen using the below give

Re: WicketTester's possible bug?

class); In development mode, this test fails, in deployment passes. Is it desirable effect or a bug? I've used Wicket 8.0.0-M5 quickstart which shows this behavior that I can provide. Thanks, Vit - To unsubscribe, e-mail: users-

Re: WicketTester's possible bug?

//start and render the test page > > tester.startPage(HomePage.class); > > > > //assert rendered page class > > tester.assertRenderedPage(HomePage.class); > > > > > &

Re: WicketTester's possible bug?

page class > tester.assertRenderedPage(HomePage.class); > > > In development mode, this test fails, in deployment passes. Is it desirable > effect or a bug? > > I've used Wicket 8.0.0-M5 quickstart which shows this behavior that I can > provide. > > Thanks, >

WicketTester's possible bug?

and render the test page tester.startPage(HomePage.class); //assert rendered page class tester.assertRenderedPage(HomePage.class); In development mode, this test fails, in deployment passes. Is it desirable effect or a bug? I've used Wicket 8.0.0-M5 quickstart which

Re: Bug in wicket 7.5.0 caused by WICKET-6231; Reported as WICKET-6266

On Tue, Nov 1, 2016 at 6:36 PM, Bas Gooren wrote: > Hi all, > > Some of our apps broke pretty badly when upgrading from 7.4.0 to 7.5.0. > > Using auto-components (which are created & added using component resolvers) > and overriding getVaration() on a parent component breaks the

Bug in wicket 7.5.0 caused by WICKET-6231; Reported as WICKET-6266

Hi all, Some of our apps broke pretty badly when upgrading from 7.4.0 to 7.5.0. Using auto-components (which are created & added using component resolvers) and overriding getVaration() on a parent component breaks the page render for us. Under these circumstances a render fails with a RTE for

Re: Bug in TreeTable example (with SelectableFolderContent)

Great, that's exactly what I did! Thanks! CN -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bug-in-TreeTable-example-with-SelectableFolderContent-tp4675396p4675404.html Sent from the Users forum mailing list archive at Nabble.com

Re: Bug in TreeTable example (with SelectableFolderContent)

Thanks! https://issues.apache.org/jira/browse/WICKET-6235 Sven On 31.08.2016 11:41, ChambreNoire wrote: Hi, I'm using Trees for the first time and I've discovered a bug with one of the examples. When using SelectableFolderContent, if one does the following : 1) select a tree node/leaf

Re: Bug in TreeTable example (with SelectableFolderContent)

I'll check what's going wrong there. Regards Sven Am 31. Aug. 2016, 11:44, um 11:44, ChambreNoire <a...@tentelemed.com> schrieb: >Hi, > >I'm using Trees for the first time and I've discovered a bug with one >of the >examples. > >When using SelectableFolderContent

Bug in TreeTable example (with SelectableFolderContent)

Hi, I'm using Trees for the first time and I've discovered a bug with one of the examples. When using SelectableFolderContent, if one does the following : 1) select a tree node/leaf 2) collapse the selected node/leaf parent (effectively making the previous selection invisible) 3) select

Re: Autocomplete has a bug

wrote: > We are running 6.20, and our test team reported a bug that corresponds to > this bugfix: > > https://issues.apache.org/jira/browse/WICKET-5882 > > However, notice the last comment from ramesh valasa. When we downloaded > 6.23 and applied it to our app, we saw the sam

Autocomplete has a bug

We are running 6.20, and our test team reported a bug that corresponds to this bugfix: https://issues.apache.org/jira/browse/WICKET-5882 However, notice the last comment from ramesh valasa. When we downloaded 6.23 and applied it to our app, we saw the same issue. Basically what happens

Re: Disabled Form Textfield and Ajax Updates / Bug or Feature?

and writes > the model object of Textfield2 (disabled). > This is working... but I'm asking myself, if this is an valid behavior. > > Is it a bug or a feature? > > Kind regards > Patrick > > - >

Disabled Form Textfield and Ajax Updates / Bug or Feature?

). This is working... but I'm asking myself, if this is an valid behavior. Is it a bug or a feature? Kind regards Patrick - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h

Re: bug of feature?

Let me see if I can do something constructive instead of just compalining On Mon, May 16, 2016 at 11:09 AM, Martin Grigorov wrote: > On Mon, May 16, 2016 at 10:59 AM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Martin, > > > > I had used this low level

Re: bug of feature?

On Mon, May 16, 2016 at 10:59 AM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Martin, > > I had used this low level API before (even before 1.5) and I always thought > that what I was doing was calling server side with some parameters It > seems I was wrong. Maybe in a future API

Re: bug of feature?

Martin, I had used this low level API before (even before 1.5) and I always thought that what I was doing was calling server side with some parameters It seems I was wrong. Maybe in a future API split this into a bind and execute? On Mon, May 16, 2016 at 9:34 AM, Martin Grigorov

Re: bug of feature?

Hi Ernesto, On Sat, May 14, 2016 at 8:59 AM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi Martin, > > Thanks for the explanation. To me is a bit weird behavior because I thought > > *Wicket*.*Ajax*.*ajax*({*"u"*:url, e: "click" , *"ep" *: {*'name'*: name, > *'type'*: type},

Re: bug of feature?

Hi Martin, Thanks for the explanation. To me is a bit weird behavior because I thought *Wicket*.*Ajax*.*ajax*({*"u"*:url, e: "click" , *"ep" *: {*'name'*: name, *'type'*: type}, *"pd"*: *true*}); Meant execute an AJAX call and inform server side about these parameter But in reality it

Re: bug of feature?

HI Ernesto, On Thu, May 12, 2016 at 5:05 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > I have a custom component which uses wicket AJAX to call server. > > *MyNameSpace.*SlimTechnologiesLazyListPanel.filter = *function*(url, elem, > event) { > *var *name =

bug of feature?

I have a custom component which uses wicket AJAX to call server. *MyNameSpace.*SlimTechnologiesLazyListPanel.filter = *function*(url, elem, event) { *var *name = *$*(elem).attr(*"techid"*); *var *type = *$*(elem).attr(*"type"*); *Wicket*.*Ajax*.*ajax*({*"u"*:url, *"ep" *: {*'name'*:

Re: AjaxCheckBox ListView Bug

Hi Sven, This solves the problem, thanks a lot for your reply ! Regards, Alexandre Le mer. 20 avr. 2016 à 18:02, Sven Meier a écrit : > Hi, > > check your markup - you should not have an id in there: > > id="all_checkboxes_have_the_same_id"/> > > Have fun > Sven > > On

Re: AjaxCheckBox ListView Bug

Hi, check your markup - you should not have an id in there: id="all_checkboxes_have_the_same_id"/> Have fun Sven On 20.04.2016 17:23, alexandre ricciardi wrote: Hello, I want to update a dropdown list with ajax calls triggered by checkboxes. I have a ListView of AjaxCheckBoxes but only

Re: AjaxCheckBox ListView Bug

Hi, Please try by calling listModules.setReuseItems(true); Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Apr 20, 2016 at 5:23 PM, alexandre ricciardi < alexandre.ricciardi.reac...@gmail.com> wrote: > Hello, > > > I want to update a dropdown list with

AjaxCheckBox ListView Bug

Hello, I want to update a dropdown list with ajax calls triggered by checkboxes. I have a ListView of AjaxCheckBoxes but only the first AjaxCheckBox is callbacked. It appears that all ajax calls are triggered by the first check box. Changing the following checkboxes have not effect.

RE: Bug in example ? repeater.DataTableFilterToolbarPage

You have right, the "size" was broken. Thanks PHL. De : Martin Grigorov <mgrigo...@apache.org> Envoyé : vendredi 4 mars 2016 07:26 À : users@wicket.apache.org Objet : Re: Bug in example ? repeater.DataTableFilterToolbarPage Hi, On Fri,

Re: Bug in example ? repeater.DataTableFilterToolbarPage

Hi, On Fri, Mar 4, 2016 at 1:44 AM, andre seame wrote: > Hello, > > > I try to understand the DataTableFilterToolbarPage. In Versin 6.21 and > 6.22. I have 2 problems : > > * If I use the date filter to get 2 anwsers, I got exception. > * If I suppress the

Bug in example ? repeater.DataTableFilterToolbarPage

Hello, I try to understand the DataTableFilterToolbarPage. In Versin 6.21 and 6.22. I have 2 problems : * If I use the date filter to get 2 anwsers, I got exception. * If I suppress the exception (see the following paragraph), the "Pager" is not updated. So I have the 2 answer on the

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

> > Thank you for your quick response! > > Best regards, Hans > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Bug-in-wicket-jqueryui-Kendo-DateTimePicker-tp4673069p4673116.html > Sent from the Users

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

Hi Hans, Kendo UI date pattern handles day names differently than java. I've fixed the issue and will deploy a snapshot tonight https://github.com/sebfz1/wicket-jquery-ui/issues/216 Thanks & best regards, Sebastien.

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

Hello Sebastien, Thank you for your quick response! Best regards, Hans -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bug-in-wicket-jqueryui-Kendo-DateTimePicker-tp4673069p4673116.html Sent from the Users forum mailing list archive at Nabble.com

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

Hello Sebastien, It's the day of the week. SimpleDateFormat's javadoc: Date and TimePattern Result "EEE, MMM d, ''yy" Wed, Jul 4, '01 Hans -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bug-in-wicket-jqueryui-Kendo-Date

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

> View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Bug-in-wicket-jqueryui-Kendo-DateTimePicker-tp4673069p4673072.html > Sent from the Users forum mailing list archive at Nabble.com. > >

Bug in wicket-jqueryui Kendo DateTimePicker?

n the picker, it shows: EEE 25 dec 2015, and the right rendering never appears again. A bug or am I doing something wrong? Regards, Hans Friederichs -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bug-in-wicket-jqueryui-Kendo-DateTimePicker-tp4673069.html Sent fro

Re: Bug in wicket-jqueryui Kendo DateTimePicker?

Hi, What EEE stands for ? Java date patterns and kendo ui date patterns are very close, so a valid java pattern should make it work. Additionnally, you can use the culture option, please look at the samples... Hope this helps, Sebastien

Re: Bug in Wicket 7.0.0-M6 and 7.0.0

Hi ! Ok, I created quickstart application, and create jira. The quickstart application has another bug (from 1.4 to 7.0.0 version): 1891.10.01 is invalid date for Wicket :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bug-in-Wicket-7-0-0-M6-and-7-0-0

Bug in Wicket 7.0.0-M6 and 7.0.0

); // border WebMarkupContainer border = new WebMarkupContainer("border"){ @Override public boolean isVisible() { return feedback.anyMessage(); // !!! BUG !!! } }; add(border); String style = "display: inline-block;"; if (width != null) style +

Re: Bug in Wicket 7.0.0-M6 and 7.0.0

ack(String id, String width) { > super(id); > // border > WebMarkupContainer border = new WebMarkupContainer("border"){ > @Override > public boolean isVisible() { > return feedback.anyMessage(); // !!! BUG !!! > } > }; > a

Re: Wicket 7.0.4M - bug related to queueing and wicket:enclosure

Thanks Andrea. On Mon, Jan 5, 2015 at 2:29 PM, andrea del bene an.delb...@gmail.com wrote: Hi, now the snapshot should work. Andrea. On 05/01/2015 11:32, mscoon wrote: Hi Martin, I just tried it with 7.0.0-SNAPSHOT and I get the same exception. I have opened

Re: Wicket 7.0.4M - bug related to queueing and wicket:enclosure

Hi Martin, I just tried it with 7.0.0-SNAPSHOT and I get the same exception. I have opened https://issues.apache.org/jira/browse/WICKET-5800 with details and a quickstart. Thanks Marios On Wed, Dec 24, 2014 at 12:33 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi, I believe this is fixed

Re: Wicket 7.0.4M - bug related to queueing and wicket:enclosure

Hi, now the snapshot should work. Andrea. On 05/01/2015 11:32, mscoon wrote: Hi Martin, I just tried it with 7.0.0-SNAPSHOT and I get the same exception. I have opened https://issues.apache.org/jira/browse/WICKET-5800 with details and a quickstart. Thanks Marios On Wed, Dec 24, 2014 at

Re: Wicket 7.0.4M - bug related to queueing and wicket:enclosure

Hi, I believe this is fixed in 7.0.0-SNAPSHOT. Please try it if you can. Thanks! On Dec 24, 2014 9:47 AM, mscoon msc...@gmail.com wrote: Hi, I have a component extending a FormComponentPanel which includes wicket:enclosures. It is embedded in tab in an ajax tabbed panel. I am getting the

Wicket 7.0.4M - bug related to queueing and wicket:enclosure

Hi, I have a component extending a FormComponentPanel which includes wicket:enclosures. It is embedded in tab in an ajax tabbed panel. I am getting the following exception when trying to change the active tab. It was working fine with wicket 6.15.0. I saw there are some issues in jira related

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

was still unclear.;-) Is it a feature or a bug, that a FormComponentFeedbackBorder surpresses the messages of its child formcomponent, which possibly could be shown by a FeedbackPanel somewhere else in the upper component hierarchy? :-) Patrick

FormComponentFeedbackBorder / missing message display / Bug or Feature?

Hi all, is it a correct behavior, a FormComponentFeedbackBorder (asterisks for form inputs) does not display a / the message in a feedbackpanel (if available somewhere)? kind regards Patrick - To unsubscribe, e-mail:

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

Hi, Please give more information. The question is not very clear. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 8, 2014 at 12:06 PM, Patrick Davids patrick.dav...@nubologic.com wrote: Hi all, is it a correct behavior, a FormComponentFeedbackBorder

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

I wrapped a formcomponent into a FormComponentFeedbackBorder to get an asterisk in case of errors. I am asking if this is a bug or a feature, because currently I am implementing a custom behavior, which adds an error message in a special-case to the component CustomBehavior.onConfigure

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 8, 2014 at 2:33 PM, Patrick Davids patrick.dav...@nubologic.com wrote: I wrapped a formcomponent into a FormComponentFeedbackBorder to get an asterisk in case of errors. I am asking if this is a bug

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

Yes, FormComponentFeedbackBorder itself just shows an asterisk. So, ok, my question was still unclear. ;-) Is it a feature or a bug, that a FormComponentFeedbackBorder surpresses the messages of its child formcomponent, which possibly could be shown by a FeedbackPanel somewhere else

Re: FormComponentFeedbackBorder / missing message display / Bug or Feature?

https://twitter.com/mtgrigorov On Mon, Dec 8, 2014 at 3:23 PM, Patrick Davids patrick.dav...@nubologic.com wrote: Yes, FormComponentFeedbackBorder itself just shows an asterisk. So, ok, my question was still unclear. ;-) Is it a feature or a bug, that a FormComponentFeedbackBorder surpresses

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

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.rich...@freenetdigital.com wrote: Hi Martin Michael, There is a bug

RE: Bug in wicket-bootstrap's Navbar

the Component itself. I think that is because of the wicket:enclosure. -Original Message- From: Martin Grigorov [mailto:mgrigo...@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

RE: Bug in wicket-bootstrap's Navbar

@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

Re: Bug in wicket-bootstrap's Navbar

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

RE: Bug in wicket-bootstrap's Navbar

Done https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/460 If you need more information please let me know. -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Monday, November 03, 2014 3:27 PM To: users@wicket.apache.org Subject: Re: Bug in wicket

Re: Potential HTTPS redirects bug with deactivated js

Hi Dmitriy, this is a bug in WebPageRenderer, so please open a Jira issue. A simple non-ajax button exposes the problem too, no need to tinker with deactivated JS: form.add(new AjaxButton(ajaxGo, form){}); form.add(new Button(go)); Please change your quickstart before

Re: Potential HTTPS redirects bug with deactivated js

Thanks for the response Sven! Issue created: https://issues.apache.org/jira/browse/WICKET-5522 Dmitriy 2014-02-27 12:22 GMT+01:00 Sven Meier s...@meiers.net: Hi Dmitriy, this is a bug in WebPageRenderer, so please open a Jira issue. A simple non-ajax button exposes the problem too

Re: Potential HTTPS redirects bug with deactivated js

for the response Sven! Issue created: https://issues.apache.org/jira/browse/WICKET-5522 Dmitriy 2014-02-27 12:22 GMT+01:00 Sven Meier s...@meiers.net: Hi Dmitriy, this is a bug in WebPageRenderer, so please open a Jira issue. A simple non-ajax button exposes the problem too, no need

Re: bug or new feature

Hi Ernesto, On Sat, Feb 22, 2014 at 8:46 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: On Wicket 6.13.0 following code script type=text/template id=message-template div class=sender pull-left div class=icon img src=img/2.jpg class=img-circle

Re: bug or new feature

3) was what i have suggested in issue... wicket:nosacan=true but for backward compatibility it would be nice if it the other way around. wicket:scan='true' On Mon, Feb 24, 2014 at 9:11 AM, Martin Grigorov mgrigo...@apache.orgwrote: Hi Ernesto, On Sat, Feb 22, 2014 at 8:46 AM, Ernesto

Re: bug or new feature

On Mon, Feb 24, 2014 at 11:56 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: 3) was what i have suggested in issue... wicket:nosacan=true but for backward compatibility it would be nice if it the other way around. wicket:scan='true' The question is: is it really needed ? I'd

Re: bug or new feature

Well I have not tried adding a CDATA but I do not see why it should not work... My point is backward compatibility. As a user this is an unexpected change: I just upgrade my application and it suddenly stops working. On Mon, Feb 24, 2014 at 10:59 AM, Martin Grigorov

Re: bug or new feature

Hi Ernesto, without having looked into this. It sound similar to: https://issues.apache.org/jira/browse/WICKET-3277 mf Am 22.02.2014 um 08:04 schrieb Ernesto Reinaldo Barreiro reier...@gmail.com: Guess %- text % is giving problems On Sat, Feb 22, 2014 at 7:50 AM, Ernesto Reinaldo

bug or new feature

On Wicket 6.13.0 following code script type=text/template id=message-template div class=sender pull-left div class=icon img src=img/2.jpg class=img-circle alt=/ /div div class=time just now /div /div

Re: bug or new feature

Maybe related to https://issues.apache.org/jira/browse/WICKET-5288 ? On Sat, Feb 22, 2014 at 7:46 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: On Wicket 6.13.0 following code script type=text/template id=message-template div class=sender pull-left div

Re: bug or new feature

Guess %- text % is giving problems On Sat, Feb 22, 2014 at 7:50 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Maybe related to https://issues.apache.org/jira/browse/WICKET-5288 ? On Sat, Feb 22, 2014 at 7:46 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: On

Re: (Probably) A Bug in AjaxLink and list

Hi Martin, Here is the java file: http://pastebin.com/rKpp50zr and the corresponding html file: http://pastebin.com/Cq1j7ZPT I have also tried with the WebMarkupContainer and had experienced the same behavior. Thanks in advance, L On Tue, Nov 5, 2013 at 2:07 PM, Martin Grigorov

Re: (Probably) A Bug in AjaxLink and list

Hi, span wicket:id=dummy id=raw/span remove id=raw and let Wicket generate the id for you On Wed, Nov 6, 2013 at 11:56 AM, lambdad...@gmail.com lambdad...@gmail.comwrote: Hi Martin, Here is the java file: http://pastebin.com/rKpp50zr and the corresponding html file:

Re: (Probably) A Bug in AjaxLink and list

That works! Thanks for your answer. cheers, L On Wed, Nov 6, 2013 at 12:37 PM, Martin Grigorov mgrigo...@apache.orgwrote: Hi, span wicket:id=dummy id=raw/span remove id=raw and let Wicket generate the id for you On Wed, Nov 6, 2013 at 11:56 AM, lambdad...@gmail.com

Re: (Probably) A Bug in AjaxLink and list

Dear Group, I haven't received any reply yet. Wasn't I clear enough in my query? cheers, L On Mon, Nov 4, 2013 at 1:00 PM, lambdad...@gmail.com lambdad...@gmail.comwrote: Hi, I am showing a list on wicket page. Each item (is a div) in the list, it has few labels and two AjaxLinks - show

Re: (Probably) A Bug in AjaxLink and list

Hi, The first mail didn't make it to the list. At least I haven't seen it. Show us your code please. On Tue, Nov 5, 2013 at 10:58 AM, lambdad...@gmail.com lambdad...@gmail.comwrote: Dear Group, I haven't received any reply yet. Wasn't I clear enough in my query? cheers, L On Mon, Nov

Possible bug with AjaxButton and textarea.

if it works, someone expert can tell me that may be happening. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Possible-bug-with-AjaxButton-and-textarea-tp4660669.html Sent from the Users forum mailing list archive at Nabble.com

Re: bug in TableComponentAsXlsHandler

Hi, On Wed, Jun 12, 2013 at 5:24 AM, grazia grazia.russolass...@gmail.comwrote: I am using the wicket poi api to generate an excel file from a PageableListView. I just run into a bug in lines 67-76 of TableComponentAsXlsHandler.java: cellExplorer becomes null already at the second

bug in TableComponentAsXlsHandler

I am using the wicket poi api to generate an excel file from a PageableListView. I just run into a bug in lines 67-76 of TableComponentAsXlsHandler.java: cellExplorer becomes null already at the second iteration of the for loop (see below) TableParser parser = new TableParser(newSheet

Re: Possible bug with AjaxLazyLoadPanel

. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Possible-bug-with-AjaxLazyLoadPanel-tp4658793p4658838.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail

Re: Possible bug with AjaxLazyLoadPanel

Michael Zhavzharov the way you've indicated, it works correctly. Thank you. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Possible-bug-with-AjaxLazyLoadPanel-tp4658793p4658846.html Sent from the Users forum mailing list archive at Nabble.com

Re: Possible bug with AjaxLazyLoadPanel

.n4.nabble.com/Possible-bug-with-AjaxLazyLoadPanel-tp4658793.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users

Re: Possible bug with AjaxLazyLoadPanel

I know how it works, in my case the component is already loaded, and I can access it, the problem is I have to access the internal components of the AjaxLazyLoadPanel. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Possible-bug-with-AjaxLazyLoadPanel

  1   2   3   4   5   6   7   8   >