You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martin Grigorov <mg...@apache.org> on 2017/03/20 08:52:17 UTC
Use jQuery 3.x by default in 8.x
Hi,
It is 14 months since Microsoft droppped the support for IE 10 and less [0].
Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
Applications will still be able to set custom version (like 1.x) if they
need so.
Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
1.
https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Sebastien <se...@gmail.com>.
Hi Korbinian,
Basically you are right : now vanilla js can almost replace jQuery (and
that's a trending as far as I can read).
But from my point of view, jQuery is more convenient to use and still has
the responsibility of the cross browser compatibility (what Wicket has
suffered before opting for jQuery)
One more important point: several integrations relies on jQuery like jQuery
UI, Kendo UI and Bootstrap (and I will not shoot myself in the foot voting
for a replacement :)).
Best regards,
Sebastien.
Re: Use jQuery 3.x by default in 8.x
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
Hi Martin,
I dont want to retire jQuery in an "get it out asap" approach, but more closely migrate away from it slowly... I mean, if you ditch jQuery it would still be needed by my own apps and a load of others, too - as it just here yet :) Basically Emond got a great idea about that!
In its own way, jQuery 3.x is breaking with backwards-compatiblity; Ditching IE is one thing, but also older mobile ones will break. Plus: once on 3.x you can't easily use older plugins
I dont care if 1.12.x is used or 3.x - but 3.x will break much more than 1.12.x would...
----- Ursprüngliche Mail -----
> Von: "Martin Grigorov" <mg...@apache.org>
> An: dev@wicket.apache.org
> Gesendet: Montag, 20. März 2017 13:01:05
> Betreff: Re: Use jQuery 3.x by default in 8.x
> On Mon, Mar 20, 2017 at 12:47 PM, Andrea Del Bene <an...@gmail.com>
> wrote:
>
>> I see your point Korbinian, but JQuery still wildly used and removing it
>> would mean not just a lot of effort, but also to indefinitely postpone the
>> release of version 8.
>>
>
> I also think it is too early to retire jQuery.
>
> But anyone can replace wicket-ajax-jquery.js with
> getJavaScriptLibrarySettings().setWicketAjaxReference(...) !
>
>
>>
>> On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl <
>> korbinian.bachl@whiskyworld.de> wrote:
>>
>> > Hi,
>> >
>> > while I'm not one of the commiters I still like to respond to this. I'm
>> > fine with changing from 1.x to 3.x as IE 10 and lower really has no
>> > relevance anymore IMHO.
>> > However, the real question that came into my mind:
>> >
>> > Why not just use plain js / vanilla js?
>> >
>> > When it was decided to go to jQuery doing pure js at that time was a
>> > nightmare - every browser had its quirks (where every is mainly that MS
>> > pile of crap called IE), reacted differently etc. - but now in 2017 I
>> dont
>> > really see so much more difference here. The same basic JS code to find a
>> > dom in every browser is just now
>> >
>> > var matches = document.querySelectorAll('div.foo');
>> >
>> > while in jQuery its
>> >
>> > var matches = $.('div.foo');
>> >
>> > - no real difference here.
>> >
>> > Ajax? -
>> >
>> > $.ajax('/user/1')
>> > .done(function (data) {
>> > var user = data;
>> > });
>> >
>> > vs
>> >
>> > fetch('/user/1')
>> > .then(function (response) {
>> > return response.json();
>> > })
>> > .then(function (data) {
>> > var user = data;
>> > });
>> >
>> >
>> > ok a small bit more and no IE support - but we just ditch that with
>> jquery
>> > 3.x anyway....
>> > (if IE is needed: ugly XMLHttpRequest)
>> >
>> > Just my 2c,
>> >
>> > Best,
>> >
>> > KB
>> >
>> >
>> >
>> >
>> > ----- Ursprüngliche Mail -----
>> > > Von: "Martin Grigorov" <mg...@apache.org>
>> > > An: dev@wicket.apache.org
>> > > Gesendet: Montag, 20. März 2017 09:52:17
>> > > Betreff: Use jQuery 3.x by default in 8.x
>> >
>> > > Hi,
>> > >
>> > > It is 14 months since Microsoft droppped the support for IE 10 and less
>> > [0].
>> > > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>> > >
>> > > Applications will still be able to set custom version (like 1.x) if
>> they
>> > > need so.
>> > > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x
>> [1].
>> > >
>> > > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-
>> IE-support
>> > > 1.
>> > > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
>> > 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>> > >
>> > > Martin Grigorov
>> > > Wicket Training and Consulting
>> > > https://twitter.com/mtgrigorov
>> >
Re: Use jQuery 3.x by default in 8.x
Posted by Martin Grigorov <mg...@apache.org>.
On Mon, Mar 20, 2017 at 12:47 PM, Andrea Del Bene <an...@gmail.com>
wrote:
> I see your point Korbinian, but JQuery still wildly used and removing it
> would mean not just a lot of effort, but also to indefinitely postpone the
> release of version 8.
>
I also think it is too early to retire jQuery.
But anyone can replace wicket-ajax-jquery.js with
getJavaScriptLibrarySettings().setWicketAjaxReference(...) !
>
> On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl <
> korbinian.bachl@whiskyworld.de> wrote:
>
> > Hi,
> >
> > while I'm not one of the commiters I still like to respond to this. I'm
> > fine with changing from 1.x to 3.x as IE 10 and lower really has no
> > relevance anymore IMHO.
> > However, the real question that came into my mind:
> >
> > Why not just use plain js / vanilla js?
> >
> > When it was decided to go to jQuery doing pure js at that time was a
> > nightmare - every browser had its quirks (where every is mainly that MS
> > pile of crap called IE), reacted differently etc. - but now in 2017 I
> dont
> > really see so much more difference here. The same basic JS code to find a
> > dom in every browser is just now
> >
> > var matches = document.querySelectorAll('div.foo');
> >
> > while in jQuery its
> >
> > var matches = $.('div.foo');
> >
> > - no real difference here.
> >
> > Ajax? -
> >
> > $.ajax('/user/1')
> > .done(function (data) {
> > var user = data;
> > });
> >
> > vs
> >
> > fetch('/user/1')
> > .then(function (response) {
> > return response.json();
> > })
> > .then(function (data) {
> > var user = data;
> > });
> >
> >
> > ok a small bit more and no IE support - but we just ditch that with
> jquery
> > 3.x anyway....
> > (if IE is needed: ugly XMLHttpRequest)
> >
> > Just my 2c,
> >
> > Best,
> >
> > KB
> >
> >
> >
> >
> > ----- Ursprüngliche Mail -----
> > > Von: "Martin Grigorov" <mg...@apache.org>
> > > An: dev@wicket.apache.org
> > > Gesendet: Montag, 20. März 2017 09:52:17
> > > Betreff: Use jQuery 3.x by default in 8.x
> >
> > > Hi,
> > >
> > > It is 14 months since Microsoft droppped the support for IE 10 and less
> > [0].
> > > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> > >
> > > Applications will still be able to set custom version (like 1.x) if
> they
> > > need so.
> > > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x
> [1].
> > >
> > > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-
> IE-support
> > > 1.
> > > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> > 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > > https://twitter.com/mtgrigorov
> >
>
Re: Use jQuery 3.x by default in 8.x
Posted by Andrea Del Bene <an...@gmail.com>.
I see your point Korbinian, but JQuery still wildly used and removing it
would mean not just a lot of effort, but also to indefinitely postpone the
release of version 8.
On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl <
korbinian.bachl@whiskyworld.de> wrote:
> Hi,
>
> while I'm not one of the commiters I still like to respond to this. I'm
> fine with changing from 1.x to 3.x as IE 10 and lower really has no
> relevance anymore IMHO.
> However, the real question that came into my mind:
>
> Why not just use plain js / vanilla js?
>
> When it was decided to go to jQuery doing pure js at that time was a
> nightmare - every browser had its quirks (where every is mainly that MS
> pile of crap called IE), reacted differently etc. - but now in 2017 I dont
> really see so much more difference here. The same basic JS code to find a
> dom in every browser is just now
>
> var matches = document.querySelectorAll('div.foo');
>
> while in jQuery its
>
> var matches = $.('div.foo');
>
> - no real difference here.
>
> Ajax? -
>
> $.ajax('/user/1')
> .done(function (data) {
> var user = data;
> });
>
> vs
>
> fetch('/user/1')
> .then(function (response) {
> return response.json();
> })
> .then(function (data) {
> var user = data;
> });
>
>
> ok a small bit more and no IE support - but we just ditch that with jquery
> 3.x anyway....
> (if IE is needed: ugly XMLHttpRequest)
>
> Just my 2c,
>
> Best,
>
> KB
>
>
>
>
> ----- Ursprüngliche Mail -----
> > Von: "Martin Grigorov" <mg...@apache.org>
> > An: dev@wicket.apache.org
> > Gesendet: Montag, 20. März 2017 09:52:17
> > Betreff: Use jQuery 3.x by default in 8.x
>
> > Hi,
> >
> > It is 14 months since Microsoft droppped the support for IE 10 and less
> [0].
> > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> >
> > Applications will still be able to set custom version (like 1.x) if they
> > need so.
> > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
> >
> > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> > 1.
> > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
>
Re: Use jQuery 3.x by default in 8.x
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
Hi,
while I'm not one of the commiters I still like to respond to this. I'm fine with changing from 1.x to 3.x as IE 10 and lower really has no relevance anymore IMHO.
However, the real question that came into my mind:
Why not just use plain js / vanilla js?
When it was decided to go to jQuery doing pure js at that time was a nightmare - every browser had its quirks (where every is mainly that MS pile of crap called IE), reacted differently etc. - but now in 2017 I dont really see so much more difference here. The same basic JS code to find a dom in every browser is just now
var matches = document.querySelectorAll('div.foo');
while in jQuery its
var matches = $.('div.foo');
- no real difference here.
Ajax? -
$.ajax('/user/1')
.done(function (data) {
var user = data;
});
vs
fetch('/user/1')
.then(function (response) {
return response.json();
})
.then(function (data) {
var user = data;
});
ok a small bit more and no IE support - but we just ditch that with jquery 3.x anyway....
(if IE is needed: ugly XMLHttpRequest)
Just my 2c,
Best,
KB
----- Ursprüngliche Mail -----
> Von: "Martin Grigorov" <mg...@apache.org>
> An: dev@wicket.apache.org
> Gesendet: Montag, 20. März 2017 09:52:17
> Betreff: Use jQuery 3.x by default in 8.x
> Hi,
>
> It is 14 months since Microsoft droppped the support for IE 10 and less [0].
> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
> Applications will still be able to set custom version (like 1.x) if they
> need so.
> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>
> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> 1.
> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Tobias Soloschenko <to...@googlemail.com>.
+1 for 3.0
> Am 20.03.2017 um 14:51 schrieb Martin Grigorov <mg...@apache.org>:
>
> Hi Emond,
>
> On Mon, Mar 20, 2017 at 2:13 PM, Emond Papegaaij <emond.papegaaij@topicus.nl <ma...@topicus.nl>
>> wrote:
>
>> Hi Martin,
>>
>> jQuery 3.x is not about dropping browser support, but changes in API. They
>> were planning
>> to have a jQuery Compat 3.x for IE8 and older, but they decided to stop
>> that just over a year
>> ago. jQuery 3.x supports the following browsers:
>> * Internet Explorer: 9+
>> * Chrome, Edge, Firefox, Safari: Current and Current - 1
>> * Opera: Current
>> * Safari Mobile iOS: 7+
>> * Android 4.0+
>>
>> You do potentially run into incompatibilities between 2.x and 3.x with
>> plugins. For this, you
>> can use the migrate plugin.
>>
>
> This is a good point!
> I know that Wicket itself works with jQuery 3.x. But you are right that
> some plugins may break.
> Even jQueryUI might break. They do not release very often lately. Same for
> many 3rd party Bootstrap plugins ...
> So maybe using 3.x as default might not be such a good idea.
>
>
>>
>> Btw. I do agree with Korbinian that we should try to use native browser
>> support if available
>> on all browsers we support. For example, querySelectorAll is available on
>> all browsers, but
>> fetch is not. Gradually changing the code to use native browser support
>> should allow us to
>> eventually remove the dependency on jQuery.
>>
>
> I am not sure #fetch() is on par with jQuery#ajax(). E.g. beforeSend()
> callback is not supported.
>
> If anyone wants to work on this then I'd prefer to create a copy of
> wicket-ajax-jquery.js and leave the jQuery impl as an alternative/fallback
> for the time being.
>
>
>>
>> Best regards,
>> Emond
>>
>> On maandag 20 maart 2017 09:52:17 CET Martin Grigorov wrote:
>>> Hi,
>>>
>>> It is 14 months since Microsoft droppped the support for IE 10 and less
>> [0].
>>> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>>>
>>> Applications will still be able to set custom version (like 1.x) if they
>>> need so.
>>> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>>>
>>> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
>>> 1.
>>> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
>> 21674d92
>>> 4d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>>>
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Martin Grigorov <mg...@apache.org>.
Hi Emond,
On Mon, Mar 20, 2017 at 2:13 PM, Emond Papegaaij <emond.papegaaij@topicus.nl
> wrote:
> Hi Martin,
>
> jQuery 3.x is not about dropping browser support, but changes in API. They
> were planning
> to have a jQuery Compat 3.x for IE8 and older, but they decided to stop
> that just over a year
> ago. jQuery 3.x supports the following browsers:
> * Internet Explorer: 9+
> * Chrome, Edge, Firefox, Safari: Current and Current - 1
> * Opera: Current
> * Safari Mobile iOS: 7+
> * Android 4.0+
>
> You do potentially run into incompatibilities between 2.x and 3.x with
> plugins. For this, you
> can use the migrate plugin.
>
This is a good point!
I know that Wicket itself works with jQuery 3.x. But you are right that
some plugins may break.
Even jQueryUI might break. They do not release very often lately. Same for
many 3rd party Bootstrap plugins ...
So maybe using 3.x as default might not be such a good idea.
>
> Btw. I do agree with Korbinian that we should try to use native browser
> support if available
> on all browsers we support. For example, querySelectorAll is available on
> all browsers, but
> fetch is not. Gradually changing the code to use native browser support
> should allow us to
> eventually remove the dependency on jQuery.
>
I am not sure #fetch() is on par with jQuery#ajax(). E.g. beforeSend()
callback is not supported.
If anyone wants to work on this then I'd prefer to create a copy of
wicket-ajax-jquery.js and leave the jQuery impl as an alternative/fallback
for the time being.
>
> Best regards,
> Emond
>
> On maandag 20 maart 2017 09:52:17 CET Martin Grigorov wrote:
> > Hi,
> >
> > It is 14 months since Microsoft droppped the support for IE 10 and less
> [0].
> > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> >
> > Applications will still be able to set custom version (like 1.x) if they
> > need so.
> > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
> >
> > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> > 1.
> > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> 21674d92
> > 4d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
>
>
>
Re: Use jQuery 3.x by default in 8.x
Posted by Emond Papegaaij <em...@topicus.nl>.
Hi Martin,
jQuery 3.x is not about dropping browser support, but changes in API. They were planning
to have a jQuery Compat 3.x for IE8 and older, but they decided to stop that just over a year
ago. jQuery 3.x supports the following browsers:
* Internet Explorer: 9+
* Chrome, Edge, Firefox, Safari: Current and Current - 1
* Opera: Current
* Safari Mobile iOS: 7+
* Android 4.0+
You do potentially run into incompatibilities between 2.x and 3.x with plugins. For this, you
can use the migrate plugin.
Btw. I do agree with Korbinian that we should try to use native browser support if available
on all browsers we support. For example, querySelectorAll is available on all browsers, but
fetch is not. Gradually changing the code to use native browser support should allow us to
eventually remove the dependency on jQuery.
Best regards,
Emond
On maandag 20 maart 2017 09:52:17 CET Martin Grigorov wrote:
> Hi,
>
> It is 14 months since Microsoft droppped the support for IE 10 and less [0].
> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
> Applications will still be able to set custom version (like 1.x) if they
> need so.
> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>
> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> 1.
> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d92
> 4d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Andrea Del Bene <an...@gmail.com>.
+1
On 20 Mar 2017 10:42, "Martijn Dashorst" <ma...@gmail.com> wrote:
> +1
>
> On Mon, Mar 20, 2017 at 9:52 AM, Martin Grigorov <mg...@apache.org>
> wrote:
> > Hi,
> >
> > It is 14 months since Microsoft droppped the support for IE 10 and less
> [0].
> > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> >
> > Applications will still be able to set custom version (like 1.x) if they
> > need so.
> > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
> >
> > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> > 1.
> > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
Re: Use jQuery 3.x by default in 8.x
Posted by Martijn Dashorst <ma...@gmail.com>.
+1
On Mon, Mar 20, 2017 at 9:52 AM, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> It is 14 months since Microsoft droppped the support for IE 10 and less [0].
> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
> Applications will still be able to set custom version (like 1.x) if they
> need so.
> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>
> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> 1.
> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: Use jQuery 3.x by default in 8.x
Posted by Martin Grigorov <mg...@apache.org>.
Thank you, all!
I've created https://issues.apache.org/jira/browse/WICKET-6341 and I will
work on it soon!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Mar 20, 2017 at 10:49 AM, Sven Meier <sv...@meiers.net> wrote:
> +1 for jQuery 3.x
>
> Sven
>
> Am 20. März 2017, 09:53, um 09:53, Martin Grigorov <mg...@apache.org>
> schrieb:
> >Hi,
> >
> >It is 14 months since Microsoft droppped the support for IE 10 and less
> >[0].
> >Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> >
> >Applications will still be able to set custom version (like 1.x) if
> >they
> >need so.
> >Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x
> >[1].
> >
> >0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> >1.
> >https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> >
> >Martin Grigorov
> >Wicket Training and Consulting
> >https://twitter.com/mtgrigorov
>
Re: Use jQuery 3.x by default in 8.x
Posted by Sven Meier <sv...@meiers.net>.
+1 for jQuery 3.x
Sven
Am 20. März 2017, 09:53, um 09:53, Martin Grigorov <mg...@apache.org> schrieb:
>Hi,
>
>It is 14 months since Microsoft droppped the support for IE 10 and less
>[0].
>Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
>Applications will still be able to set custom version (like 1.x) if
>they
>need so.
>Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x
>[1].
>
>0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
>1.
>https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
>Martin Grigorov
>Wicket Training and Consulting
>https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Sebastien <se...@gmail.com>.
+1 too!
On Mon, Mar 20, 2017 at 10:01 AM, Emond Papegaaij <
emond.papegaaij@topicus.nl> wrote:
> Agreed, +1 for 3.x
>
> Emond
>
> On maandag 20 maart 2017 09:52:17 CET Martin Grigorov wrote:
> > Hi,
> >
> > It is 14 months since Microsoft droppped the support for IE 10 and less
> [0].
> > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> >
> > Applications will still be able to set custom version (like 1.x) if they
> > need so.
> > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
> >
> > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> > 1.
> > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> 21674d92
> > 4d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
>
>
>
Re: Use jQuery 3.x by default in 8.x
Posted by Emond Papegaaij <em...@topicus.nl>.
Agreed, +1 for 3.x
Emond
On maandag 20 maart 2017 09:52:17 CET Martin Grigorov wrote:
> Hi,
>
> It is 14 months since Microsoft droppped the support for IE 10 and less [0].
> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
> Applications will still be able to set custom version (like 1.x) if they
> need so.
> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>
> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> 1.
> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d92
> 4d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
Re: Use jQuery 3.x by default in 8.x
Posted by Maxim Solodovnik <so...@gmail.com>.
+1 for 3.0 :)
On Mon, Mar 20, 2017 at 3:52 PM, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> It is 14 months since Microsoft droppped the support for IE 10 and less [0].
> Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
>
> Applications will still be able to set custom version (like 1.x) if they
> need so.
> Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x [1].
>
> 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support
> 1.
> https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c79421674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
--
WBR
Maxim aka solomax