Set Focus to Modal Window Title
Hey Everyone,
I'm having some difficulties with *ModalWindow*. I need a way to set the
*HTML Focus* to the *title* of the *ModalWindow* when it pops up, but so far
nothing has worked for me.
1. I have tried adding an *AjaxEventBehavior ("onload")* to my modal window,
but that did not work. Neither did ("onchange") or ("onblur").
2. I have also tried appending javascript to the target when invoking the
ModalWindow's *show() *method:
...but unfortunately *this.getMarkupId()* is referring to the div holding
the wicket component:
...and not the actual Modal Window itself, which is dynamically creating
id's like so:
3. I have also tried using *AjaxRequestTarget.focusComponent()*:
...where *child()* is simply returning the first component in the hierarchy
that is not a *WebMarkupContainer*:
Using the Wicket Ajax Debug window, we can see that my 3rd attempt did
successfully fire some javascript to set focus:
BUT when I use the Internet Explorer developer tools and run
*document.activeElement*, I am returned the entire body of the web page,
meaning there is no focus set.
If anyone can think of a way to set focus on the modal window title, or a
way to hardcode id's for different parts of the modal window, please help me
out. Thanks!
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Setting focus on a ModalWindow title
Hey Everyone,
I'm having some difficulties with *ModalWindow*. I need a way to set the
HTML Focus to the title of the *ModalWindow *when it pops up, but so far
nothing has worked for me.
1. I have tried adding an *AjaxEventBehavior ("onload")* to my modal window,
but that did not work. Neither did *("onchange")* or *("onblur")*.
2. I have also tried appending javascript to the target when invoking the
ModalWindow's *show()* method:
...but unfortunately this.getMarkupId() is referring to the div holding the
wicket component:
...and not the actual Modal Window itself, which is dynamically creating
id's like so:
3. I have also tried using *AjaxRequestTarget.focusComponent()*:
...where *child()* is simply returning the first component in the hierarchy
that is not a WebMarkupContainer:
Using the Wicket Ajax Debug window, we can see that my 3rd attempt did
successfully fire some javascript to set focus:
BUT when I use the Internet Explorer developer tools and run
*document.activeElement*, I am returned the entire body of the web page,
meaning there is no focus set.
If anyone can think of a way to set focus on the modal window title, or a
way to hardcode id's for different parts of the modal window, please help me
out. Thanks!
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Disable component to prevent double click
You can override public CharSequence getAfterHandler(Component component) instead to disable the button *after* the Ajax call is made. Martin Grigorov Wicket Training and Consulting Looking for a remote position with Wicket ? Contact me! https://twitter.com/mtgrigorov On Wed, Feb 21, 2018 at 8:34 PM, Claudia Hirt wrote: > Thanks for your answer. Your tip for non-ajax-buttons helped me a lot. > Just another remark about that: disabling a Button in getTriggerJavaScript > leads to the side effect that the onsubmit method of the Button will not be > called because the disabling is done before form submit. > The css property pointer-events does the trick in most cases but is poorly > supported in Internet Explorer. > I‘ll keep on trying... > > Best regards, > Claudia Hirt > > > Am 20.02.2018 um 16:02 schrieb Andrea Del Bene : > > > > Hi, > > > > as reported in its javadoc AjaxDisableComponentListener by default uses > the > > DOM attribute 'disabled' to do its job, but this attribute doesn't work > > with links. For this kind of components you have to provide the right > > JavaScript to enable/disable them by overriding > generateHandlerJavaScript. > > Id you are not using AJAX you can not use this behavior and you must > > provide the JavaScript code in some other way. For example with > SubmitLink > > you have to override getTriggerJavaScript. Unfortunately "disabling" a > html > > component is not a standard procedure so for those components that don't > > support the attribute 'disabled' we must use custom JavaScript. > > > >> On Mon, Feb 19, 2018 at 9:55 PM, Claudia Hirt > wrote: > >> > >> By the way: is there any reason why AjaxDisableComponentListener has no > >> public constructor? > >> > >>> Am 19.02.2018 um 21:49 schrieb Claudia Hirt : > >>> > >>> Hi all, > >>> I‘m facing the problem of double submits when double clicking on > buttons > >> and links. I was very pleased to see there’s a new listener of > >> https://issues.apache.org/jira/browse/WICKET-6448 implemented in wicket > >> 7.10. But this only works for Buttons not for links like a SubmitLink. > I‘m > >> also facing the same issue for non-ajax-components. > >>> Any suggestions how to solve this? > >>> Thanks in advance! > >>> Best regards, Claudia > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Disable component to prevent double click
Thanks for your answer. Your tip for non-ajax-buttons helped me a lot. Just another remark about that: disabling a Button in getTriggerJavaScript leads to the side effect that the onsubmit method of the Button will not be called because the disabling is done before form submit. The css property pointer-events does the trick in most cases but is poorly supported in Internet Explorer. I‘ll keep on trying... Best regards, Claudia Hirt > Am 20.02.2018 um 16:02 schrieb Andrea Del Bene : > > Hi, > > as reported in its javadoc AjaxDisableComponentListener by default uses the > DOM attribute 'disabled' to do its job, but this attribute doesn't work > with links. For this kind of components you have to provide the right > JavaScript to enable/disable them by overriding generateHandlerJavaScript. > Id you are not using AJAX you can not use this behavior and you must > provide the JavaScript code in some other way. For example with SubmitLink > you have to override getTriggerJavaScript. Unfortunately "disabling" a html > component is not a standard procedure so for those components that don't > support the attribute 'disabled' we must use custom JavaScript. > >> On Mon, Feb 19, 2018 at 9:55 PM, Claudia Hirt wrote: >> >> By the way: is there any reason why AjaxDisableComponentListener has no >> public constructor? >> >>> Am 19.02.2018 um 21:49 schrieb Claudia Hirt : >>> >>> Hi all, >>> I‘m facing the problem of double submits when double clicking on buttons >> and links. I was very pleased to see there’s a new listener of >> https://issues.apache.org/jira/browse/WICKET-6448 implemented in wicket >> 7.10. But this only works for Buttons not for links like a SubmitLink. I‘m >> also facing the same issue for non-ajax-components. >>> Any suggestions how to solve this? >>> Thanks in advance! >>> Best regards, Claudia >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] Apache Wicket 6.29.0 released
The Apache Wicket PMC is proud to announce Apache Wicket 6.29.0! Apache Wicket is an open source Java component oriented web application framework that powers thousands of web applications and web sites for governments, stores, universities, cities, banks, email providers, and more. You can find more about Apache Wicket at https://wicket.apache.org This release marks another minor release of Wicket 6. We use semantic versioning for the development of Wicket, and as such no API breaks are present breaks are present in this release compared to 6.0.0. Using this release -- With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): org.apache.wicket wicket-core 6.29.0 Or download and build the distribution yourself, or use our convenience binary package * Source: http://www.apache.org/dyn/closer.cgi/wicket/6.29.0 * Binary: http://www.apache.org/dyn/closer.cgi/wicket/6.29.0/binaries Upgrading from earlier versions --- If you upgrade from 6.y.z this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at * http://s.apache.org/wicket6migration Have fun! — The Wicket team The signatures for the source release artefacts: Signature for apache-wicket-6.29.0.zip: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhrh0QAKXGaVgypdlZgaK5b6M3Fxgu S5LW18OjhEQFQ4yYuz6CE3C/L54u6K4Es6SBhUgAVGuLwaRBdflOfcNA7DRm0Imh rHcssI6bt7DBxEjIu+XmXEqfgSmZ3P3VQQWGbPtbSMYBXSjhhYFdb8D286U0ec3T f/vD28ZZmdvRV7NuMKUe54cyMXFebmSfutwQWZqKs/Gx/HOZh4cU2lBbmLvPOuvy aT1nN7kLhrxROvzOgoyAOo5Dv7HlFrs7eJFQXr1Resz1FTMJrP6sNAQpY3QlcYUa rORqmxp8H4mXbSVkLk4Kquu6Q6tOcbijUZPZC4Vm5W+xPsBZrsYtJF8S76GZlbq1 tBKlkmwweX/MirHnLwqHaMm43iz7dyf6FS5C9qi0j4GmMKGSh+Lv7Sk1wP3bvyc2 80loN03gJYCxrse7PcqO65STBjQ8fZlhpHt8yVxwdKJexPJd/aHJHmnoMsJ1FfHj LxNlHyya34XTpSZBE8Q+Qv47MOLsvGrkbD0876YwjMSQtDX9cUrRC95Hvtvxmqgm w9GlnnDY8q4Ts9ZZeJSDbanPY3zmAkVrpg+yqlY/pZsFCqh8Wv3L5DUNh+3cUBX+ B7UyK+DJCXOld+81tESZWZhHAN6DXZWrWANrrtkeWO3qtdNLZTaOMAHaaoHPWJEK xo2Iapi8IzjYJr5jN7nq =ZuKl -END PGP SIGNATURE- Signature for apache-wicket-6.29.0.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJaiFhXAAoJEIePAfqo01bhPY8P/j6Lwdz9Swa/mHs6EagLTq0s iArc8ZQzlt8GtnpVr6IIngDcFwvhvsWqCtSpPFmUt74xtZbA6oz6GBhEE0Dmsr9x 93Ov2aKYRU1pR/H5VkNWqdR67J6QT4amE81T+RzbfQbvcP7YFIIbPOTg4ox3Za61 fu2NlkzB4u9qiPfqad6ylGoVu4mUde+klsnQiHL2dA3DmucChG08I9xjgzqQDIwo ph2gbieag9RjbgRQEKOYOQcBBS7B8VCNvFxslbchGJEQm6B2QVuQV3+nvyWbjQ0J u0tpbZA0Wev59dzpLRJDSFcccgBCCII+MP9RZPRuQSUDAyIg/PJ1LFtm/85hxV7C VqDTMuniLYZT8shTWw4VKQfVGmjso/eRQsNAG7BeMZqxBWQpQQ+6BMoy2piXAavp RZxO17Ct0V9dPVp7cTTHiet/Iz1oPwkceF5KmaQl1vLhicBbvLF6993ny7iP0Lyo t+Jh1v4TFf7Daxxgl6q1tO2zDZc94877FXwjZ7b/n37SoRENzTPj+sNhpS3jCZ+E QxXp/dYU0L6+mVLhJ4XPWAsTljdvnXwHf7S1RBSeEsGb9BM97l6Yh2WpWTgvLiwy lvdWNkWX1pd6fD1V/XT83FtlQDURPkGN6Bbbfmwh8pSPbzQMn2Q5EXlFTLcTsVhW QV/yE6KsG5K8AqjY9DdD =oA/r -END PGP SIGNATURE- CHANGELOG for 6.29.0: ** Bug * [WICKET-6484] - Wicket.Cookie.set does not set 'secure' flag * [WICKET-6501] - DefaultPageManagerProvider does not honour StoreSettings.setAsynchronous(false) * [WICKET-6526] - Ajax Buttons do not check for the HTTP method and thus don't respect Form#onMethodMismatch * [WICKET-6530] - Race-condition in session invalidation - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
FINAL REMINDER: CFP for Apache EU Roadshow Closes 25th February
Hello Apache Supporters and Enthusiasts This is your FINAL reminder that the Call for Papers (CFP) for the Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018 in Berlin. Note that the CFP deadline has been extended to *25*^*th* *February *and it will be your final opportunity to submit a talk for thisevent. Please make your submissions at http://apachecon.com/euroadshow18/ Also note that early bird ticket registrations to attend FOSS Backstage including the Apache EU Roadshow, have also been extended and will be available until 23^rd February. Please register at https://foss-backstage.de/tickets We look forward to seeing you in Berlin! Thanks Sharan Foga, VP Apache Community Development PLEASE NOTE: You are receiving this message because you are subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects.
Re: Modifying componentfeedbackpanel output
no tags :((( Maybe you can create quickstart project with 1) desired structure 2) your subclass On Wed, Feb 21, 2018 at 11:01 PM, Entropy wrote: > I'm not sure how to make the markup show right in the post. I'll try > wrapping it in PRE. > > > > > //Error: This field is required. > > > > > Anyway, yes, I am subclassing the component feedback, but it adds the > controls and iterates to produce the messages. If I just modify the > contents of that inner span in the html, of course it overwrites everything. > I would need to get control when the individual message is being worked on, > AND then inject my boilerplate. > > Fortunately, that inner stuff doesn't need to change per message or > anything. Just structure so the message will render how they want. > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modifying componentfeedbackpanel output
I'm not sure how to make the markup show right in the post. I'll try wrapping it in PRE. //Error: This field is required. Anyway, yes, I am subclassing the component feedback, but it adds the controls and iterates to produce the messages. If I just modify the contents of that inner span in the html, of course it overwrites everything. I would need to get control when the individual message is being worked on, AND then inject my boilerplate. Fortunately, that inner stuff doesn't need to change per message or anything. Just structure so the message will render how they want. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modifying componentfeedbackpanel output
It is hard to read your markup :(
You can extend FeedbackPanel and provide your own markup
Would it work?
On Wed, Feb 21, 2018 at 10:10 PM, Entropy wrote:
> Ooops, I see nabble is hiding the tags. Trying again with < and >
>
>
>
> aria-hidden="true" class="fas fa-exclamation-triangle" title="Error
> ">Error: This field is
> required.
>
>
>
>
>
>
> --
> Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
--
WBR
Maxim aka solomax
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modifying componentfeedbackpanel output
Ooops, I see nabble is hiding the tags. Trying again with < and >
Error: This field is
required.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Modifying componentfeedbackpanel output
Our front-end guy is asking for us to modify how our component feedback messages render. In particular he wants tags around EACH MESSAGE like so: //Error: This is the message. I added an override for the ComponentFeedbackPanel java and html to make everything spans, and I see onComponentTag as a way to add attributes to the top level span, but I am not sure how to get access to the individual message spans or how to write the extra tags before and after the message. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
