Deprecate jQuery.browser

[mako281@…]

Add Google Chrome to jQuery.browser, that is all :)

[john]

Nominating ticket for 1.7 discussion.

[rwaldron]

-1, Adding new support to jQuery.browser might be perceived as encouragement to use it.

[jaubourg]

-1,

[timmywil]

-1, I wish jQuery.browser wasn't there.

[paul.irish]

-1

(While I'm on the Chrome team, this is my personal opinion)

$.browser.safari was renamed to webkit a few versions ago to preempt this request.

[dmethvin]

+1, Gentlemen, what are our intentions with respect to jQuery.browser? If we are going to let it languish then let's just yank it with the reasoning that we aren't maintaining it anyway. The docs say it will be a supported plugin eventually. Will the plugin return Chrome?

[john]

-1, I'd prefer to stop updating jQuery.browser

[addyosmani]

-1

[ajpiano]

+1, Totally agree with Dave here. If it's there, it should at least be sensible. Otherwise, let's actually get rid of the damn thing.

[scott.gonzalez]

+0

[ThiefMaster]

+1, sometimes there are browser bugs which are not testable through $.support

[rwaldron]

 https://github.com/jquery/jquery/pull/417

[Dave Methvin]

Merge pull request #417 from rwldrn/9385

Begrudgingly adds chrome detection to jQuery.browser (1.7). Fixes #9385

Changeset: 5417a2cf6b629b5bf3103454a5a6cab2181924e8

[Krinkle]

What about Safari ? Now there's Chrome but no Safari, that's odd/annoying. Perhaps add back safari as well ?

[timmywil]

Revert "Updated version numbers; Fixes #9385"

This reverts commit 09fe3ea265d730cc5e2dd2705d5a60ffd382d166.

Changeset: e2187f49637c62d9b72ec852c9213a20778e63d3

[timmywil]

Revert "Begrudgingly adds chrome detection to jQuery.browser (1.7). Fixes #9385"

This reverts commit dd93d0eb32dc638ff3319792a885acd6d3c25c30.

Changeset: 2a045f8269de9ef936bfaa2efbf71b9962385cf8

[timmywil]

Reopened for 1.7.

[mikesherov]

+1, If we're going to have a jQuery.browser at all, it should be able to detect Chrome. This vote becomes a -1 if instead we decide to gut jQuery.browser completely.

[mikesherov]

-1, Changing to -1 because I just saw that moving jQuery.browser to a compatibility plugin was up for a vote. :-)

[jaubourg]

+0, if we move $.browser to an official plugin, then we can have this kind of change. Else, no.

[dmethvin]

We voted this down in 1.7 but if we are planning to abandon maintenance of jQuery.browser we should determine a sunset version and get rid of it.

Our current docs say it will be turned into a plugin, I think the community's assumption would be that it is an official and maintained plugin. If we aren't going to maintain this we need to say so ASAP and provide other alternatives to avoid breaking code. (Although if it uses jQuery.browser it's already broken ... ba-dum-pum!)

[jzaefferer]

-1, deprecated already anyway

[timmywil]

-1, Never ever

[rwaldron]

-1, still opposed.

[rwaldron]

#11181 is a duplicate of this ticket.

[dmethvin]

OK, we're keeping this in as-is for 1.8 but will trumpet that it is being removed into a plugin as of 1.9. It is already deprecated in the docs.

[dmethvin]

 https://github.com/louisremi/jquery.browser

[dmethvin]

There will be a separate  plugin as of 1.8, and jQuery.browser will disappear from core as of 1.9. You can include the plugin as of 1.8 if desired, or substitute your own flaky-and-fragile regex for our flaky-and-fragile regex, or (even better) just stop using browser sniffing.

[rwaldron]

Plugin for 1.8 and on

 https://github.com/jquery/jquery-browser

[dmethvin]

There are some unit tests that need to use a different check, such as window.opera for jQuery.browser.opera.

[dmethvin]

Duly and exhaustively deprecated. The jQuery.browser repo will be merged into the backcompat repo when it's created.