+1 for 3.0
> Am 20.03.2017 um 14:51 schrieb Martin Grigorov <mgrigo...@apache.org>:
>
> Hi Emond,
>
> On Mon, Mar 20, 2017 at 2:13 PM, Emond Papegaaij <emond.papega...@topicus.nl
> <mailto:emond.papega...@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
