# Vivaldi, Windows Mobile and Edge not detected

**URL:** <https://meta.discourse.org/t/vivaldi-windows-mobile-and-edge-not-detected/102282>\
**Category:** Feature\
**Created:** [11월 18, 2018, 10:32오후 UTC](https://meta.discourse.org/t/vivaldi-windows-mobile-and-edge-not-detected/102282 "2018-11-18T22:32:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesus2099](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jesus2099/32/119720_2.png) [@jesus2099](https://meta.discourse.org/u/jesus2099)\
**Post date:** [11월 18, 2018, 10:32오후 UTC](https://meta.discourse.org/t/vivaldi-windows-mobile-and-edge-not-detected/102282/1 "2018-11-18T22:32:05Z")

</div>

Hello,

I use two main OS and browsers (I paste user agents for the record):

- **Edge** on **Windows 10 Mobile** (Lumia phone)  
`Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; Microsoft; Lumia 640 LTE Dual SIM) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Mobile Safari/537.36 Edge/15.15063`
- [Vivaldi](https://vivaldi.com) on **Windows 7**  
`Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Vivaldi/2.1.1337.36`

But in the two Discourse sites I use, [**MetaBrainz** running Discourse **2.2.0.beta3**](https://community.metabrainz.org/u/jesus2099/preferences/account) and [**meta** running Discourse **2.2.0.beta4**](https://meta.discourse.org/u/jesus2099/preferences/account), in **Recently Used Devices** section:

- **Vivaldi** is seen as **Google Chrome** on both Discourse sites
- **Windows 10 Mobile** is seen as **Android Device** on both Discourse sites
- **Edge** is seen as **Google Chrome** on **2.2.0.beta3** (seems OK **Microsoft Edge** on **2.2.0.beta4** , though)

* * *

Vivaldi [does not occur](https://github.com/discourse/discourse/search?q=vivaldi&unscoped_q=vivaldi) anywhere in code.

For Windows Phone detection, I do see it, but maybe it’s not used in **Recently Used Devices** screen:

> <https://github.com/discourse/discourse/blob/597f1709953d2c466bf55f87efb1660d02f04a71/app/assets/javascripts/discourse/pre-initializers/sniff-capabilities.js.es6#L21>

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [11월 19, 2018, 5:51오전 UTC](https://meta.discourse.org/t/vivaldi-windows-mobile-and-edge-not-detected/102282/2 "2018-11-19T05:51:58Z")

</div>

We don’t want to go down this path though:

 ![image](https://global.discourse-cdn.com/meta/original/3X/4/d/4dc56bcdf1c9a0a77b7bef97e384c177ba98c69e.png)

Vivaldi is at 0.05% market share, we ought to do Yandex and UC Browser well before it, and then when do we stop? At the moment to keep things simple our detection simply should stop at Opera, which technically is almost Chrome cause it runs Blink but still.

Windows mobile is almost dead, Microsoft started killing it in 2017.

The only impact of these nits are cosmetic in the list of sessions.

---

<div class="post-metadata">

**Author:** ![jesus2099](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jesus2099/32/119720_2.png) [@jesus2099](https://meta.discourse.org/u/jesus2099)\
**Post date:** [11월 19, 2018, 8:13오전 UTC](https://meta.discourse.org/t/vivaldi-windows-mobile-and-edge-not-detected/102282/3 "2018-11-19T08:13:24Z")

</div>

> [@sam](#):
>
> The only impact of these nits are cosmetic in the list of sessions.

Oh yes, absolutely, I just wanted to note it down somewhere in case someone else is wondering why their sessions look like this.

Discourse works wonderfully good under those anyway (probably because they seem based on Chrome).

I am not expecting a fix if it’s only for the session list.  
I thought maybe you were using those for stats as well, or something, so it could worth letting you know. 🙂  
It’s why I just wrote this under #Contribute > Feature (_Discussion about existing Discourse features, how they can be improved or enhanced, and how proposed new features could work._) and not under #Contribute > Bug. 🙂
