Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Changes to BlackBerry smartphone and Playbook User Agent detection #2505

Closed
anonymous-piwik-user opened this Issue · 5 comments

2 participants

Anonymous Piwik user Anthon Pang
Anonymous Piwik user

Currently the BlackBerry Playbook isn't detected correctly (shows Safari 0.0 as Browser and Device unknown), this is what the user agent looks like:


Your user agent: Mozilla/5.0 (PlayBook; U; RIM Tablet OS 1.0.0; en-US) AppleWebKit/534.11+ (KHTML, like Gecko) Version/0.0.1 Safari/534.11+

Browser info:
array
'id' => string 'SF' (length=2)
'name' => string 'Safari' (length=6)
'short_name' => string 'Safari' (length=6)
'major_number' => string '0' (length=1)
'minor_number' => string '0' (length=1)
'version' => string '0.0' (length=3)

Operating System info:

boolean false

A proper Icon for the Playbook could be the current iPad icon or maybe this one: http://de.blackberry.com/devices/blackberrytorch/appworld_icon.jpg

Anthon Pang
Collaborator

I'll have to mull this over. The Playbook could be orphaned by the time 1.6 comes out... ;)

Version 0.0 is correct imo since it is an override and we don't parse the third component of versions, eg 4.1.0 and 4.1.2 both simplified to 4.1.

Anonymous Piwik user

Hopefully not ;)

The question is if maybe in case of this special behaviour the version number could be cut off to avoid confusion, and just have it as Safari or Safari for Playbook/Safari Mobile, something like this.

The Safari for BB handhelds reports correctly with version 6 + release numbers...

Anthon Pang
Collaborator

(In [4947]) fixes #2505

Anthon Pang
Collaborator

reopening re: comment:2 BB smartphones shouldn't be shown as Safari 6 -- this is reserved for Apple releases.

Anthon Pang
Collaborator

(In [4948]) fixes #2505 - revamped BB detection/parsing

Anonymous Piwik user anonymous-piwik-user added this to the 1.5.1 Piwik 1.5.1 milestone
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.