UA Parsing Is Incorrect - Blackberry Torch

[GoogleCodeExporter]

Safari 6.0.0 is not Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en-US) 
AppleWebKit/534.1  (KHTML, like Gecko) Version/6.0.0.91 Mobile Safari/534.1 
,gzip(gfe),gzip(gfe)

Thuis is the wekbit browser on the blackberry torch (blackberry OS 6.0)

Original issue reported on code.google.com by alu...@gmail.com on 12 Nov 2010 at 6:42

[GoogleCodeExporter]

Original comment by els...@gmail.com on 18 Nov 2010 at 5:30

• Changed title: UA Parsing Is Incorrect - Blackberry Torch

[GoogleCodeExporter]

Do we want to call out the BlackBerry Torch specifically?  If not, UA string 
appears to be correctly caught by the BlackBerry parser; I'm not sure how it 
was identified as Safari, as it correctly comes up at 
http://www.browserscope.org/ua.

Original comment by drewgstephens on 20 Nov 2010 at 10:08

[GoogleCodeExporter]

I wasn't suggesting it should be called out as a Torch specifically. The 
notable thing about the Torch is, as the only 6.0 device available, it's the 
only webkit-based BB browser out there - if it's identified as BB 6.0.0, that's 
sufficient.

I submitted the original issue from a link at jsperf.com; unfortunately 
encoding that link changed the UA string. The string that the BB browser 
reports is 
Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en-US) AppleWebKit/534.1+ (KHTML, 
like Gecko) Version/6.0.0.91 Mobile Safari/534.1+,gzip(gfe),gzip(gfe)
(note: "534.1+" instead of "534.1")

This UA, which was parsed by browserscope/ua?o=js to Safari 6.0.0, is indeed 
read as Safari 6 when submitted through the web interface (browserscope.org/ua)

Original comment by alu...@gmail.com on 21 Nov 2010 at 4:03

[GoogleCodeExporter]

This bug gets at the heart of something we're doing imprecisely in Browserscope 
today with UA identification. I think we need to start parsing platform(os), 
product and render engine - this distinction is especially poignant for mobile 
where we're about to see a variety of OS/browser combinations. Android can run 
a few different browsers for instance. Today we pretty much try to show 
product, but we should migrate to something more robust. Interestingly, Drew 
(on this thread) is extracting the UA parser out of Browserscope and I think we 
can and should consider making some changes in this regard to try to solve this 
overarching issue soon.

Original comment by els...@gmail.com on 21 Nov 2010 at 5:46

[GoogleCodeExporter]

Original comment by els...@gmail.com on 17 Mar 2012 at 7:22

• Changed state: Fixed