Side navigation
#8115 closed enhancement (fixed)
Opened February 01, 2011 07:35AM UTC
Closed February 01, 2011 03:01PM UTC
Last modified March 19, 2012 09:25PM UTC
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.
Attachments (0)
Change History (5)
Changed February 01, 2011 07:36AM UTC by comment:1
| component: | unfiled → ajax |
|---|---|
| owner: | → jaubourg |
| priority: | undecided → low |
| status: | new → assigned |
| type: | bug → feature |
Changed February 01, 2011 10:06AM UTC by comment:2
| type: | feature → enhancement |
|---|
Changed February 01, 2011 11:37AM UTC by comment:3
| milestone: | 1.next → 1.5.1 |
|---|
Changed February 01, 2011 12:16PM UTC by comment:4
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.