Linked by Thom Holwerda on Fri 6th Jan 2012 17:47 UTC
Permalink for comment 502461
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-01-25
I don't know the details of how the UA strings are parsed by the tool they used, but as far as Chromium goes if it is a "vanilla" build it will be indistinguishable from Chrome - the UA strings are constructed identically.
However, Chromium is often packaged by 3rd parties and they do sometimes modified the UA string. Ubuntu for example adds a chromium specific identifier "Chromium/xx.xxx", which does not actually exist in vanilla builds. It still contains the "Chrome/xx.xxx" identifier though, which is what most UA detection routines would pick up on and identify it as Chrome.
I would say in all likelihood that yes, Chromium usage would be bundled with the Chrome numbers.