Skip to main content

Bug Tracker

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:

We completely forgot about the existence of and it seems like a reasonable change to avoid confusion.

Attachments (0)
Change History (5)

Changed February 01, 2011 07:36AM UTC by jaubourg comment:1

component: unfiledajax
owner: → jaubourg
priority: undecidedlow
status: newassigned
type: bugfeature

Changed February 01, 2011 10:06AM UTC by jaubourg comment:2

type: featureenhancement

Changed February 01, 2011 11:37AM UTC by jitter comment:3

milestone: 1.next1.5.1

Changed February 01, 2011 12:16PM UTC by jitter 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.

Changed February 01, 2011 03:01PM UTC by jaubourg comment:5

resolution: → fixed
status: assignedclosed

Fixes #8115. Renames all references to jXHR with jqXHR in the code (like was done in the doc).

Changeset: cb49b4a1b648dea8ce5b1e5dbb2ab5432a84cb63