[
https://issues.apache.org/jira/browse/WICKET-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127811#comment-15127811
]
Martin Grigorov commented on WICKET-6086:
-----------------------------------------
Can you reproduce this with any of the wicket-examples?
Wicket 7.2.0 uses jQuery 1.12.0 / 2.2.0. I haven't noticed any problems in my
main application so far. You can use
application.getJavaScriptLibrarySettings().setJQueryReference() to downgrade
jQuery to 1.11.3 / 2.1.3 in the meantime. But I think a bug report should be
reported to jQuery / the jQuery plugin instead, not to Wicket.
> Upgrade leads to jquery errors
> ------------------------------
>
> Key: WICKET-6086
> URL: https://issues.apache.org/jira/browse/WICKET-6086
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 7.2.0
> Reporter: Daniel Jipa
>
> Some components that worked fine with 7.1.0 are leading to jquery errors in
> 7.2.0 release.
> This can be reproduced with the select2 extension, but also some other jquery
> components leads to the same error.
> Error is something like that:
> Wicket.Ajax: Wicket.Ajax.Call.processEvaluation: Exception evaluating
> javascript: TypeError: view is null
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
