The jquery statement
$(selector).find(":input[data-val=true]").each(....) - line 173 jquery.validate.unobtrusive.js within the Parse(selector) method.
Provides better performance if it is re-written as a chained statement, oppose to as a single selector:
$(selector).find("input").filter["data-val=true]").each(..)
This is because it allows JQuery to use less of the Sizzle engine (which is known to be poor). On a large DOM, it has shown performance improvements of an order of magnitude firing the DOMContentLoaded event.
We have reduced the duration of our Document ready method from 700ms to 300ms.
Thanks,
Comments: Hi, I checked the latest NuGet package, and found the change that Ryan made there. And, I'm closing this bug. Please feel free to reactivate this bug whenever you have more issue/suggestion/or comment to address. Thanks, Youngujune
$(selector).find(":input[data-val=true]").each(....) - line 173 jquery.validate.unobtrusive.js within the Parse(selector) method.
Provides better performance if it is re-written as a chained statement, oppose to as a single selector:
$(selector).find("input").filter["data-val=true]").each(..)
This is because it allows JQuery to use less of the Sizzle engine (which is known to be poor). On a large DOM, it has shown performance improvements of an order of magnitude firing the DOMContentLoaded event.
We have reduced the duration of our Document ready method from 700ms to 300ms.
Thanks,
Comments: Hi, I checked the latest NuGet package, and found the change that Ryan made there. And, I'm closing this bug. Please feel free to reactivate this bug whenever you have more issue/suggestion/or comment to address. Thanks, Youngujune