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
Baseline query #771
Comments
We can add alias for I, honestly, don’t like Baseline, since it looks like too US centric for me. There are no browsers popular in Asia and Africa there. Should we wait a little to see how popular it will be? |
Waiting seems fine to me, especially since users already have the ability to query for those browsers as you described! |
I think an alias would be helpful, as it's already being actively used by web.dev and MDN. However, this could make it harder to support versioned Baseline lists: web-platform-dx/web-features#264 (comment)
According to Statcounter Global Stats, Chrome still has over 70% market share in Asia and Africa. I believe most of the other popular mobile browsers in these regions are based on Chromium, which is already in Baseline.
I'd argue it's already getting popular, considering it's already been added to many articles on web.dev and MDN, and the WebDx Community Group running it already has 2 chairs and 42 other participants from at least 11 organizations. |
This is not really accurate and doesn't carry any weight. The people behind the WebDx Community Group and web.dev and MDN are the same.
Baseline only includes latest 2 Chrome majors, so any Chromium based browser that is a little bit more behind (e.g. Samsung Internet with ±5% market share) is excluded. In reality Baseline excludes a lot more people than it includes.
It's too soon to create an alias as the definition of Baseline isn't even stable yet. At this time Baseline is harmful towards end users and hostile towards browser vendors not included in their list. They are very actively working on a better definition. |
Perhaps there could be separate lists or envs with more relaxed versioning based on usage of release dates of browser versions. |
That is what is being researched in the WebDx community group. |
The definition was updated and in a very specific way. https://web.dev/blog/baseline-definition-update
I don't think Browserslist doesn't know anything about features. Tools like |
@romainmenke how we can select browsers? Can you show an example? I do not see any logic in queries like |
For example with
But I don't see how this can be easily used by developers. |
@romainmenke the browsers you need can be selected by old query like How Baseline criteria be used here to select browsers? I think we can use Baseline only to select features by browsers list, not in opposite way. |
Yeah, exactly. I think this needs to be implemented in individual tools. |
I think I am confusing myself with the overly complex wording of the definition. On second thought I think it is as simple as : List all versions for Safari, Firefox, Chrome of the last 30 months for both desktop and mobile. Is there any practical example where that would yield a different outcome? They did not expand the set of browsers to include options that are popular in non-western regions but they did address this. 30 months is considered to be a proxy metrics that should in practice cover sufficient users, regardless of the actual browser they use. You can still find significant segments that fall outside of this definition. |
It seems like it might be useful to provide a "baseline" query to account for the target browsers of https://web.dev/baseline/!
The text was updated successfully, but these errors were encountered: