Skip to content
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

Request: Break down the userAgent string for easy aggregation #100

Open
merlinstardust opened this issue May 19, 2016 · 3 comments
Open
Labels
good first issue Good issue for new commers to this project

Comments

@merlinstardust
Copy link
Collaborator

I'd love to see the UserAgent string broken down into more fields. This would allow a developer to easily write queries and aggregations based on the different parts of the string. I'd love to use this to see how many users are on a particular platform. But right now this is difficult because if a user happens to use safari/601.1 and another uses safari 600.1, these strings are considered separate even though the browser is still Safari.

Based on the Wikipedia explanation of the different parts, you could have

userAgent: {
  fullString: 'Mozilla/5.0 (iPad; U; CPU OS 3_2_1 like Mac OS X; en-us) AppleWebKit/531.21.10 (KHTML, like Gecko) Mobile/7B405',
  systemDetails: 'iPad; U; CPU OS 3_2_1 like Mac OS X; en-us',
  browserPlatform: {
    name: 'AppleWebKit'
    version: '531.21.10',
  }
  browserPlatformDetails: 'KHTML, like Gecko',
  enhancements: 'Mobile/7B405',
}
@StorytellerCZ StorytellerCZ added the good first issue Good issue for new commers to this project label Oct 21, 2019
@sufisaid
Copy link

sufisaid commented Oct 8, 2020

Hello.
Is this something you still plan to do?
There could be some good implementation.

@sebakerckhof
Copy link

I don't think this still makes sense since user agent is deprecated:
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ

@sufisaid
Copy link

sufisaid commented Oct 8, 2020

Although, this is only an idea. Apple had the same idea in 2017. but when they were informed regarding the impact of that change, they gave up on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good issue for new commers to this project
Projects
None yet
Development

No branches or pull requests

4 participants