#8115 closed enhancement (fixed)
jXHR to be changed to jqXHR in both docs and code
| Reported by: | jaubourg | Owned by: | jaubourg |
|---|---|---|---|
| Priority: | low | Milestone: | 1.5.1 |
| Component: | ajax | Version: | 1.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
We completely forgot about the existence of http://mulletxhr.com/ and it seems like a reasonable change to avoid confusion.
Change History (5)
comment:1 Changed 13 years ago by
| Component: | unfiled → ajax |
|---|---|
| Owner: | set to jaubourg |
| Priority: | undecided → low |
| Status: | new → assigned |
| Type: | bug → feature |
comment:2 Changed 13 years ago by
| Type: | feature → enhancement |
|---|
comment:3 Changed 13 years ago by
| Milestone: | 1.next → 1.5.1 |
|---|
comment:4 Changed 13 years ago by
comment:5 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixes #8115. Renames all references to jXHR with jqXHR in the code (like was done in the doc).
Changeset: cb49b4a1b648dea8ce5b1e5dbb2ab5432a84cb63
Note: See
TracTickets for help on using
tickets.
I don't know if the naming conflict is really this bad. It's not like we did it on purpose.
We should evaluate how big the damage might for jQuery by renaming our
jXHR. Basically every blog post about 1.5b1-1.5 contains jXHR referring to the new returned XHR wrapper of$.ajax(). Renaming it now to something else might create some confusion.It maybe not too late to change it, as long as not a jQuery related page is #1 result on google for jXHR.