Replying to [comment:1 gnarf]:
You want something along the lines of: "The page referenced by the URL will not be loaded until the tab is selected (which may be immediately if no other tabs exist)" on the docs for the add method?
Yes, that would work. Note that
add() actually calls
load(). I can't see how an ajax request could already be active when
add() is called, but I just wanted to point that out.
I think that the "load" method calling
.abort() could actually be considered a bug... The behavior probably exists for the case when someone clicks quickly between two tabs to cancel the 'useless' request before sending a new one, but I think that manual calls to "load" should just start a request for that content, and perhaps even in the double navigation cancel it may be worth it to just load the content anyway - you already made the request...
But again, it would be the
select() method that cancels existing requests, not
load(). I can completely understand the thinking behind having an existing request canceled, I just think it belongs in
select() instead of in
load(). Note that moving the call to
select() means your existing scenario stays the same, but programmatic uses of
load() allow for multiple simultaneous requests...