Mike XenForo developer Staff member Nov 3, 2010 #2 Fixed now, looks like it might've been triggered by a change in jQuery and our expectations of a return value.
Fixed now, looks like it might've been triggered by a change in jQuery and our expectations of a return value.