Add Vivaldi browser

[Christoph142]

Vivaldi browser is the spiritual successor of Opera. It's growing quickly and should be included.

[Fyrd]

As a Chromium-based browser it's unlikely that Vivaldi will be included. Too much duplicate information. It's more likely that Opera will some day be dropped for the same reason.

[Christoph142]

I was wondering right from the start why it says Chrome and Opera instead of Chromium. It should be split into browser engines and not browsers then... ;)

[Djaler]

But developers don't know which version of chromium corresponds to which version of vivaldi

[tiritto]

Like Djaler said, Vivaldi support would be great addition to the list. While it's true that it uses Chromium engine just like Chrome, we can't be so sure about feature availability because newest version of one browser might still use older version of the engine than chrome does. The only fair solution is either replacing Chrome category with Chromium or adding other chromium-based browsers to the mix.

[Seb35]

A solution could be to add "chromium" as a category inherited by "chrome", "vivaldi", "brave", "opera", etc with a mapping between Chromium versions and Chrome/Vivaldi/Brave/Opera 15+/etc versions. Said differently, "chromium" would be a fallback of "vivaldi" translated to the corresponding version.

I’m not sure how easy it is to retrieve the mappings between Chromium and Chrome/Vivaldi/Brave/Opera/etc versions. I guess there is a 1:1 mapping between Chromium and Chrome; it seems available in the package.json file for Brave (and hence the history can be reconstructed), and I see it is written in the about of my Vivaldi browser (but I don’t know if the history is easily available).

[Djaler]

I solve my problem by using obsolete-webpack-plugin. It checks not for browser version, but for kernel version (https://github.com/ElemeFE/obsolete-webpack-plugin#faq-tea). It's possible because, for example, chrome-based browsers like Vivalde have in theirs useragents version of chrome. Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.143 Safari/537.36 Vivaldi/1.95.1077.45

[sxiii]

As @Seb35 says I also feel that Vivaldi should be included in a category inherited by Chromium. I use this browser as one of my main on a daily basis, and same stand for brave.

[voxpelli]

But developers don't know which version of chromium corresponds to which version of vivaldi

This feels like the core issue to me, but also like an issue that isn't really for CanIUse to solve.

There could be another resource somewhere – which CanIUse, Browserslists or others can consume – that links the version of a Chromium based browser to a Chromium version, like a chromium-version-mapper project. (Could maybe be semi-automated using https://github.com/wavebox/chromium-detector)

Such a project could solve this issue, the Brave request (#2749, https://github.com/browserslist/browserslist/issues/578), the MS Edge request (#5492) etc – all without bloating CanIUse. It could also allow for tracking more obscure browsers, like https://github.com/beakerbrowser/beaker

[whut]

Interesting data point to share: browsers support for PWA Add to Home screen feature. This differentiates Chrome, Opera and Vivaldi browsers:

• Chrome supports it ✔️
• Opera does not ❌
• Vivaldi supports it ✔️ (reference)

On CanIUse page I see only first two: web app manifest