From 7ada7ba0f169e8a122b87846644e5df249f44477 Mon Sep 17 00:00:00 2001 From: Jake Boone Date: Thu, 27 Oct 2011 14:53:45 -0400 Subject: [PATCH] Grammar correction --- docs/pages/page-navmodel.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/page-navmodel.html b/docs/pages/page-navmodel.html index b10378d0..4ecea08e 100644 --- a/docs/pages/page-navmodel.html +++ b/docs/pages/page-navmodel.html @@ -120,7 +120,7 @@ $.ajaxPrefilter( function(options, originalOptions, jqXHR) {

Setting isLocal to true for your ajax requests will alert jQuery Core that it should handle the 0 return values differently. Local requests exhibit similar behavior (ie 0 statuses), and Core will then fall back to determining success based on the presence of content in the xhr responseText attribute.

-

One important issue to note with the above is that it will set isLocal to true for all requests made via ajax regardless of whether they are in the manifest or not so long as the cache is valid. This works for now because Core only consults the isLocal value when the status is in fact 0 which doesn't affect uncached results. There is no long term guarantee that isLocal will remain isolated in it's purpose for handling 0 status values. If that changes it may break your application.

+

One important issue to note with the above is that it will set isLocal to true for all requests made via ajax regardless of whether they are in the manifest or not so long as the cache is valid. This works for now because Core only consults the isLocal value when the status is in fact 0 which doesn't affect uncached results. There is no long term guarantee that isLocal will remain isolated in its purpose for handling 0 status values. If that changes it may break your application.

Known limitations