-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*minor*: $.support vs $.browser #2
Comments
As the docs http://api.jquery.com/jQuery.browser/ say: So it's not really deprecated, it's just not recommended to use it. But as there is no other way to detect hash history support it's quite reliable way for this. Especially that it's only needed for old browsers and there is no risk that any new browser will not work. The idea behind $.support is great, but there are some cases where it's impossible (or very very hard) to use it. It's not worth to create some big and heavy support test (including iframes, additional requests and stuff) just to check if browser is IE<8. |
This is definitely something I'm looking into but I don't see it happening in the foreseeable future. There are too many browser and version specific cases that $.support simply doesn't handle especially when it comes to detecting Opera or older versions of Safari. I'll leave the issue open because there is space for improvement. Things will get easier if one day we drop the support for some old browser versions. |
The use of Line 410
Change to
|
Hello. ASUAL, I recently came up with how to use jquery you can determine, exactly what version of IE is used. I suggest you use it (because it is more reliable than the User Agent):
I'll be glad if you use it |
As$.support really doesn't give you any clues as to whether or not a browser will support tracking hash history, or what lengths you need to go to to work around the lacking support for mocking the history, I can 100% see why you are using $ .browser and not $.support.
That said, $.browser IS deprecated. Any plans of moving off it?
The text was updated successfully, but these errors were encountered: