Re: wicket8 : wickets js/ jquery integration

Oktober 2017 22:22:56 Betreff: Re: wicket8 : wickets js/ jquery integration Hi Korbinian, using the "defer" attribute on script tags in the head section seems to be best practice now: https://www.shivering-isles.com/the-science-of-loading-javascript/ Wicket supports the attribute since

Re: wicket8 : wickets js/ jquery integration

Oktober 2017 22:22:56 > Betreff: Re: wicket8 : wickets js/ jquery integration > Hi Korbinian, > > using the "defer" attribute on script tags in the head section seems to > be best practice now: > > https://www.shivering-isles.com/the-science-of-loadin

Re: wicket8 : wickets js/ jquery integration

Is the such option for CSS as well? I have implemented "delayed load" manually since both JS and CSS were reported as "blocking scripts" On Sun, Oct 8, 2017 at 12:25 PM, Martin Grigorov wrote: > On Oct 7, 2017 23:23, "Sven Meier" wrote: > > Hi

Re: wicket8 : wickets js/ jquery integration

On Oct 7, 2017 23:23, "Sven Meier" wrote: Hi Korbinian, using the "defer" attribute on script tags in the head section seems to be best practice now: The problem is that the ondomready scripts depend on jquery and wicket-xyz ones and there is no way to defer them.

Re: wicket8 : wickets js/ jquery integration

Hi Korbinian, using the "defer" attribute on script tags in the head section seems to be best practice now: https://www.shivering-isles.com/the-science-of-loading-javascript/ Wicket supports the attribute since https://issues.apache.org/jira/browse/WICKET-5715 Have fun Sven Am

wicket8 : wickets js/ jquery integration

Hi, currently wicket renders all its jQuery and Ajax stuff right into the head, and I wonder why. Current best practice seems to defer all javascript till the end of the page just right before the closing tag to let the browser meanwhile get the DOM and do some work and not get blocked by