I think you probably want to use document.location.href which is the
string representation of the location object.
Also, jus as an aside, document.location is actually a deprecated
alias (by spec) to the real window.location, so you might consider
updating your references to window. instead of
We're struggling with the best way to inform .ajax() that we expect
multiple data types. Either, with a setting like auto or by passing an
array of data types (or maybe allowing both).
Perhaps it would help if we defined a list of goals. I'll start.
1. $.ajax() - if dataType has not been
John,
While I'm glad to see a scope arg available, i still think this is negligent
to the future of jQuery and ES standards. I really think a fn.bind()
implementation would ideal (since it would be jQuery-wide and not just
available in one function), but as I've noted in the past and is exampled
This page:
http://docs.jquery.com/Traversing/contains
needs to be removed from the docs. (Only a sysop can do this)
It is not currently accessible from the main Traversing index, but it
still exists and someone came in yesterday wondering why this didn't
work in jQuery 1.3.2.
FWIW, this is how
Rick, your 1 (which I too have suggested in the past) might bring about
unease as folks would prefer any eval-ing to come through explicit request.
I also think it's imperative that the behavior of any dataType setting
(including null) shouldn't change (especially to one that suddenly evals!).
But
I can compromise with your #2, and give them both my vote.
Passing it on...
*1. Allow $.ajax() to accept multiple expected dataTypes.
2. Setting to have $.ajax() auto-detect/translate via response content-type
header.*
Julian - your thoughts?
On Mon, Dec 28, 2009 at 3:39 PM, webbiedave
Actually, I think you are right in line with the rest of us.
Rick
On Mon, Dec 28, 2009 at 4:11 PM, Erik Beeson erik.bee...@gmail.com wrote:
Again, why not do this with an Accept header?
Client sends acceptable content types, server responds with a content type,
if the server's response is
deleted
--Karl
On Dec 28, 2009, at 3:19 PM, ajpiano wrote:
This page:
http://docs.jquery.com/Traversing/contains
needs to be removed from the docs. (Only a sysop can do this)
It is not currently accessible from the main Traversing index, but it
still exists and someone came in yesterday
I made a simplified page to demonstrate this behavior. Unfortunately, that
page doesn't exhibit the behavior. *sigh*. I'll keep investigating. In
the mean time, if anyone has ever seen this kind of behavior and knows why
it happened to them, their feedback would be appreciated.
On Sun, Dec 27,
I made a post about how confusing people may find the name bind some
time ago. Suggested renaming bind to something like event, and keeping
bind as an alias of course. That was rejected.
I don't get what you are talking about a fn.bind() implementation in
jQuery, or what you mean by available
Available, as in the scope argument is being retrofitted to an existing
function, and ONLY to that function.
I don't get what you are talking about a fn.bind() implementation in
jQuery, or what you mean by available in just one function though.
Read ES5.
function.prototype.bind()
On Mon,
Rick Waldron wrote:
Available, as in the scope argument is being retrofitted to an
existing function, and ONLY to that function.
I don't get what you are talking about a fn.bind() implementation in
jQuery, or what you mean by available in just one function though.
Read ES5.
12 matches
Mail list logo
