Similar to #970 this is the rollup of all the deprecations planned for jQuery 3.2 and 3.3 to be sure we don't miss any. We have tickets in the Core tracker for these and a few have their own docs tickets already.

jQuery 3.2

• jQuery.holdReady (PR All: Updates for jQuery 1.12/2.2-3.5 #1160)

jQuery 3.3

• Event shorthand methods (see below) (issue Document deprecation of event shorthands like jQuery.fn.click() #1205)
• jQuery.isArray (issue Deprecate jQuery.isArray docs changes #950, PR All: Updates for jQuery 1.12/2.2-3.5 #1160)
• jQuery.isNumeric (issue Deprecate jQuery.isNumeric docs changes #949, PR All: Updates for jQuery 1.12/2.2-3.5 #1160)
• jQuery.now (issue Deprecate jQuery.now docs changes #947, PR All: Updates for jQuery 1.12/2.2-3.5 #1160)
• [jQuery.proxy](Deprecate jQuery.proxy jquery#2958, PR All: Updates for jQuery 1.12/2.2-3.5 #1160)
• event.which (see also Deprecate which property of the event object jquery#2337) (EDIT by @mgol: this API got undeprecated)
• .hover (covered by Document deprecation of event shorthands like jQuery.fn.click() #1205)

For the event shorthand methods (.click(), .mousemove(), etc.) I think we should use the current API entries and explain that .click() is now best done as .on("click", fn) or .trigger("click"). However let's just rewrite the examples and discussion in those pages to use .on() or .trigger() and describe the behavior of the event since I think people still want/need those event-specific details.