Vulnerable jQuery version
-
- PrimeFaces Core Developer
- Posts: 3979
- Joined: 03 Dec 2010, 14:11
- Location: Bavaria, DE
- Contact:
Great, so please come back if you have some news to share!
Thomas Andraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
We have a similar problem with jQuery 1.11.3.
We have to migrate an application from Richfaces to Primefaces, but jquery 1.11.3 would give us problems with the security team. So we would like to upgrade to jQuery 1.12.4.
I already tested primefaces with jQuery 1.12.4 and did not find problems in my test application. But then I read, that the oncomplete function could be broken (https://github.com/primefaces/primefaces/issues/2233). Do you have any experiences, which problems arise with jQuiery 1.12.4 or is there a concrete bug list?
Thanks in advance,
jemie
We have to migrate an application from Richfaces to Primefaces, but jquery 1.11.3 would give us problems with the security team. So we would like to upgrade to jQuery 1.12.4.
I already tested primefaces with jQuery 1.12.4 and did not find problems in my test application. But then I read, that the oncomplete function could be broken (https://github.com/primefaces/primefaces/issues/2233). Do you have any experiences, which problems arise with jQuiery 1.12.4 or is there a concrete bug list?
Thanks in advance,
jemie
PrimeFaces Developer | PrimeFaces Extensions Developer
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
GitHub Profile: https://github.com/melloware
PrimeFaces Elite 13.0.0 / PF Extensions 13.0.0
PrimeReact 9.6.1
Wow... such a major update in a 'minor' release where no-one of the community can get hold of... I think this would justify an additional community release (just like I always found it 'good' to after some weeks a small bugfix release would be justified)
-
- Information
-
Who is online
Users browsing this forum: No registered users and 27 guests