Skip to content

Update api entries with 1.9 upgrade guide info #240

Closed
dmethvin opened this Issue Jan 28, 2013 · 8 comments

3 participants

@dmethvin
jQuery Foundation member

This could be broken into separate issues if that's more convenient.

  • .toggle(function, function, ... ) removed
  • jQuery.browser() removed
  • .live() removed
  • .die() removed
  • jQuery.sub() removed
  • .add()
  • .addBack( selector ) replaces .andSelf()
  • .after(), .before(), and .replaceWith() with disconnected nodes http://bugs.jquery.com/ticket/13338
  • .appendTo, .insertBefore, .insertAfter, and .replaceAll
  • AJAX events should be attached to document
  • Checkbox/radio state in a .trigger()ed "click" event
  • Order of triggered "focus" events
  • jQuery(htmlString) versus jQuery(selectorString)
  • Events not fired by the .data() method; names with periods
  • Ordering of disconnected nodes within a jQuery set
  • Loading and running scripts inside HTML content
  • .attr() versus .prop()
  • $("input").attr("type", newValue) in oldIE
  • "hover" pseudo-event
  • .selector property on jQuery objects
  • jQuery.attr()
  • jQuery.ajax returning a JSON result of an empty string
  • jQuery.proxy() context
  • .data("events")
  • Removed properties of the Event object
@dmethvin
jQuery Foundation member

We never documented .data()-fired events and I haven't seen any complaints so I'm not going to document they were removed.

@poloniculmov poloniculmov added a commit to poloniculmov/api.jquery.com that referenced this issue Apr 23, 2013
@poloniculmov poloniculmov gh-240; jQuery 1.9 wants document for ajax events
Updated the exemple to reflect the change in Jquery 1.9 that the Ajax events should be attached to the document.
923f28e
@dmethvin dmethvin added a commit that referenced this issue May 19, 2013
@poloniculmov poloniculmov Ref gh-240; jQuery 1.9 wants document for ajax events. Close gh-285.
Updated the example to reflect the change in jQuery 1.9.
dmethvin: changed "broadcast" to "trigger" event terminology.
ca266fb
@jzaefferer
jQuery Foundation member

@dmethvin any chance you or someone else from the core team could finish this? "Ordering of disconnected nodes within a jQuery set" is interesting to me, since I recently hit a performance issue involving .add().

@dmethvin
jQuery Foundation member

Where would be the right place to put the note about ordering? It applies to all methods. I think that .add() needs special notice since it's better to use $([ a, b ]) than $(a).add(b) if you want a specific order.

@scottgonzalez
jQuery Foundation member

I'm not sure the best way to document the general rule, but just adding a sentence about the array usage not forcing DOM order is a step in the right direction. We use this in UI when we want to have a manually ordered set.

@dmethvin
jQuery Foundation member

We can mention that in jQuery() then. Since we got rid of the special behavior of .before() etc on disconnected elements I think .add() is a somewhat unique lone survivor so I can mention it there.

@jzaefferer
jQuery Foundation member

Down to just three open tasks, nice.

@dmethvin
jQuery Foundation member
@jzaefferer
jQuery Foundation member

You can deploy manually to stage to test your changes or show them to others. Not great in the long run, but better then nothing. Ping me elsewhere if you need the credentials.

@dmethvin dmethvin closed this Jan 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.