$.browser

$.browser

Removing the $.browser feature may not have been a very good move (and does it really save a lot on file size?). I fully realize that for many things "feature detection" is better but there are still rare instances where you really do need to find out what the browser is. This is illustrated by the topic I raised on Stack Overflow about Firefox sometimes adding in unwanted BR tags. Because of that bug I now have to use $.browser to supply scripting for only Firefox. As far as I know there is no way to feature detect if a browser adds in unwanted BR tags.

http://stackoverflow.com/questions/14105890/jhtmlarea-adding-unwanted-br-tag/

Additionally I believe that even though Chrome and Safari both use webkit that there are still some rare instances where they behave differently, so that there may also be occasions when Safari needs to be targeted but not Chrome, and vice versa.

I'm not talking about "branching code" here so that different browsers have wildly different code served up to them. I'm talking about being able to deal with some rare but fine-grained browser differences.