Opened 7 years ago
Closed 7 years ago
#12032 closed bug (wontfix)
$.browser.safari returns true in latest Chrome release
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.7.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The latest Chrome release for Mac (20.0.1132.47) looks like it changed it's user agent string and is causing jQuery's $.browser.safari function is returning true.
Change History (3)
comment:1 Changed 7 years ago by
| Owner: | set to bryan@… |
|---|---|
| Status: | new → pending |
comment:2 Changed 7 years ago by
Yeah I've already figured out my own detection in the meantime, here's the user agent string the current Chrome build spits out:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_0) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11
comment:3 Changed 7 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | pending → closed |
This is because $.browser is unmaintained - to maintain is to encourage its use. Don't use it.
Note: See
TracTickets for help on using
tickets.
I wouldn't count on this being the last time, you can use
navigator.userAgentto directly sniff out whatever you think is a more accurate detection.Can you provide the full user agent for your browser?