Jaxel Well-known member Dec 27, 2013 #1 Open up chrome inspector on any xenforo page and you will find this error in the console log. Looks like it will need to be future proofed.
Open up chrome inspector on any xenforo page and you will find this error in the console log. Looks like it will need to be future proofed.
Mike XenForo developer Staff member Dec 28, 2013 #2 I'm pretty sure this is simply inherent to jQuery itself, though I'd have to double check.
Pereira Well-known member Dec 29, 2013 #3 Apparently it's a jQuery bug http://bugs.jquery.com/ticket/14282 It's been marked as fixed in jQuery 1.11/2.1
Apparently it's a jQuery bug http://bugs.jquery.com/ticket/14282 It's been marked as fixed in jQuery 1.11/2.1
Chris D XenForo developer Staff member Dec 29, 2013 #4 I can confirm that jQuery 1.11.0 beta 3 resolves the issue. I can also confirm that, so far in my testing, jQuery 1.11.0 appears to work fine with XenForo.
I can confirm that jQuery 1.11.0 beta 3 resolves the issue. I can also confirm that, so far in my testing, jQuery 1.11.0 appears to work fine with XenForo.
thedude Well-known member Jan 24, 2014 #5 http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/ The official release of 1.11 came out today and this issue is fixed in it, like Chris and Pereira pointed out
http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/ The official release of 1.11 came out today and this issue is fixed in it, like Chris and Pereira pointed out