Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

browserl.ist returns incorrect Edge versions

See original GitHub issue

Steps to reproduce:

Go to this page: https://browserl.ist/?q=last+2+Edge+versions

Current behaviour:

It returns Edge versions 18 and 17

Expected behaviour:

It should return Edge versions 83 and 81 See https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel

Edit: From command line it works fine:

$ npx browserslist "last 2 Edge versions"
edge 83
edge 81

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

masicommented, Feb 16, 2021

I was also wondering if a LegacyEdge name wouldn’t make rules easier.

0reactions

isvladxxecommented, Oct 28, 2020

All old CI expected behaviour 17, 18, but now it is broken. My colleagues from the previous project contacted me about this issue.

no matter how much I dislike to support edgeHtml, there are platforms that are never updated to edge chromium (like vin7, it etc) which are, for example, in offices or universities where they have no rights to install software, and sometimes there really are no system administrators (post ussr location) it is expected that the EdgeHtml engine will be used and with the arrival of security updates it will be updated and the CI will work “edge chromium” needs new separate tag or EdgeHtml needs its own