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

Consider "families" of browsers (or hook into the concept of "navigator compatibility mode") #177

Open
miketaylr opened this issue Feb 3, 2022 · 4 comments

Comments

@miketaylr
Copy link
Member

Right now we talk about Chrome, Firefox, Safari... but there are obviously other browsers like Edge, Opera, Waterfox, Epiphany, etc. We should look to see if they follow a stable pattern and document it if so.

@gsnedders
Copy link
Member

This is with regards to UA strings, I presume?

As @domenic said in #168 (comment):

We could also probably say something useful about the crossover with the navigator compatibility mode.

@karlcow
Copy link
Member

karlcow commented Feb 10, 2022

@gsnedders yes we were saying during the meeting than giving examples only for Safari, Chrome and Firefox and not other browsers seem a bit strange. So we were wondering if there was a larger pattern where we could add a keyword for specializing the UA string.

For example for Chromium based browser, there is an additional token at the end of the string.

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4851.0 Safari/537.36 Edg/100.0.1158.0

For Gecko based browsers, there is also a similar pattern

Mozilla/5.0 (X11; FreeBSD amd64; rv:56.0) Gecko/20100101 Firefox/56.0 Waterfox/56.2.14

@karlcow
Copy link
Member

karlcow commented Jun 24, 2022

I think @gsnedders recently looked at the UA strings for different apps using WKWebView.
Could you share here what you got in patterns?

@miketaylr miketaylr changed the title Consider "families" of browsers Consider "families" of browsers (or hook into the concept of "navigator compatibility mode") Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants