SOLVED

Fix sites detecting MS Edge as a Google Chrome browser

%3CLINGO-SUB%20id%3D%22lingo-sub-1271575%22%20slang%3D%22en-US%22%3EFix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271575%22%20slang%3D%22en-US%22%3E%3CP%3ELike%20others%20I%20find%20most%20of%20the%20browser%20detecting%20sites%20report%20that%20we%20are%20using%20a%20Google%20Chrome%20Browser%20that's%20really%20annoying.%20Now%20this%20is%20a%20problem.%20We%20love%20MS%20Edge%20and%20sites%20should%20also%20show%20what%20we%20are%20using!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20hampers%20MS%20Edge%20popularity%20and%20market%20share%20statistics%20.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suggest%20that%20MS%20Edge%20team%20fix%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271633%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271633%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20actually%20%3CEM%3Eis%3C%2FEM%3E%20reporting%20edge%20in%20its%20user%20agent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20original%20edge%20used%20to%20say%20'Edge'%20in%20its%20user%20agent%2C%20now%20its%20displaying%20'Edg'%20instead%2C%20this%20is%20mainly%20because%20of%20compatibility%3B%20given%20all%20the%20standardizing%20issues%20with%20the%20legacy%20Edge%2C%20most%20sites%20would%20display%20older%20forms%20or%20simply%20refuse%20to%20support%20edge.%3C%2FP%3E%3CP%3EThose%20sites%20may%20have%20not%20been%20updated%20in%20years%2C%20so%20even%20if%20the%20problems%20with%20that%20browser%20were%20solved%20they'd%20still%20behave%20the%20same%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20prevent%20this%20from%20happening%20edge%20is%20now%20reporting%20'Edg'.%3C%2FP%3E%3CP%3ENewer%20sites%20should%20have%20no%20problems%20recognizing%20it%20as%20-the%20new-%20Microsoft%20Edge.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOlder%20ones%20may%20think%20its%20an%20unsupported%20browser%2C%20but%20because%20edge%20also%20has%20%3CSPAN%3EChrome%20in%20its%20user%20agent%2C%20they%20will%20identify%20it%20as%20Chrome%20%3CEM%3Ecompatible.%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChecking%20and%20blocking%20based%20on%20user%20agents%20is%20not%20the%20best%20practice%2C%20and%20considering%20how%20user%20agents%20are%20being%20deprecated%20soon%20(i%3CEM%3E.e%3C%2FEM%3E%20they%20will%20only%20be%20used%20to%20check%20between%20mobile%2Fdesktop%20devices%2C%20and%20for%20backwards%20compatibility%20%3CSTRONG%3Ethe%20browser's%20version%2Fname%20will%20stay%20'frozen'%3C%2FSTRONG%3E)%20this%20should%20not%20cause%20any%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271668%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271668%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F379650%22%20target%3D%22_blank%22%3E%40VioletVillain%3C%2FA%3E%26nbsp%3BSadly%20it%20seems%20most%20popular%20browser%20detecting%20sites%20have%20not%20been%20updated%20yet.%20Because%20they%20are%20still%20showing%20it%20as%20a%20Chrome%20browser.%20It's%20sad%20to%20see%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271694%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271694%22%20slang%3D%22en-US%22%3EHmm%2C%20most%20show%20Edge%20to%20me.%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20it%20really%20should%20not%20cause%20any%20problems%2C%20since%20user%20agents%20are%20soon%20getting%20deprecated%20anyway%20and%20the%20browser's%20name%2Fversion%20will%20stay%20frozen%20at%20a%20certain%20version.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20they%20won't%20stay%20a%20viable%20method%20to%20compare%20browsers'%20usages.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271997%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271997%22%20slang%3D%22en-US%22%3EHello%2C%3CBR%20%2F%3EWhich%20channel%2Fversion%20are%20you%20using%3F%3CBR%20%2F%3Ethe%20user%20agent%20looks%20fine%20in%2083.0.471.0%3CBR%20%2F%3Eedge%3A%2F%2Fversion%2F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1273677%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1273677%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3Bdev%2083.0.467.0%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1273935%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1273935%22%20slang%3D%22en-US%22%3EWhich%20sites%20detect%20Edge%20by%20mistake%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1274449%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1274449%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3Ba%20quick%20google%20search%20%22Check%20my%20browser%20name%22%20tools%20reveal%20these%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1274504%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1274504%22%20slang%3D%22en-US%22%3E%3CP%3EThose%20websites%20are%20most%20likely%20old%20and%20fail%20to%20detect%20the%20%3CU%3Enew%3C%2FU%3E%20Edge%20browser%3C%2FP%3E%3CP%3Elooking%20at%20the%20browser%20string%20everything%20looks%20fine%3C%2FP%3E%3CP%3E%3CA%20href%3D%22edge%3A%2F%2Fversion%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eedge%3A%2F%2Fversion%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%224.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181569iBB1C542D20B9FD04%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%224.png%22%20alt%3D%224.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%221.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181568iC705E78E1A884276%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%221.png%22%20alt%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%222.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181570i50730AC3DD0426D9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222.png%22%20alt%3D%222.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%223.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181571iF9EF25E71D7ABC9C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%223.png%22%20alt%3D%223.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1274563%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1274563%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F597187%22%20target%3D%22_blank%22%3E%40HereItis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOkay%20I%20actually%20found%20out%20why%20those%20websites%20are%20showing%20the%20incorrect%20browser%3A%3C%2FP%3E%3COL%3E%3CLI%3EThey%20are%20old.%3C%2FLI%3E%3CLI%3EThose%20website%20developers%20haven't%20updated%20the%20code%20in%20their%20websites%20to%20detect%20the%20new%20Edge%20browser%20which%20has%20a%20different%20UA.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fmsedgedev%2F2019%2F04%2F08%2Fmicrosoft-edge-preview-channel-details%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.windows.com%2Fmsedgedev%2F2019%2F04%2F08%2Fmicrosoft-edge-preview-channel-details%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId-415613620%22%20id%3D%22toc-hId-415613620%22%20id%3D%22toc-hId-415613620%22%20id%3D%22toc-hId-415613620%22%3EUser%20Agent%20String%3C%2FH1%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20Microsoft%20Edge%20adopting%20Chromium%2C%20we%20are%20changing%20our%20user%20agent%20string%20to%20closely%20resemble%20that%20of%20the%20Chromium%20user%20agent%20string%20with%20the%20addition%20of%20the%20%E2%80%9CEdg%E2%80%9D%20token.%20If%20you%E2%80%99re%20blocking%20site%20access%20on%20user%20agent%20strings%2C%20please%20update%20your%20logic%20to%20treat%20this%20string%20as%20another%20Chromium-based%20browser.%3C%2FP%3E%3CP%3EBelow%20is%20the%20user%20agent%20string%20for%20the%20latest%20Dev%20Channel%20build%20of%20Microsoft%20Edge%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EMozilla%2F5.0%20(Windows%20NT%2010.0%3B%20Win64%3B%20x64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3729.48%20Safari%2F537.36%20Edg%2F74.1.96.24%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3E%3CSTRONG%3EWe%E2%80%99ve%20selected%20the%20%E2%80%9C%3CFONT%20color%3D%22%23FF0000%22%3EEdg%3C%2FFONT%3E%E2%80%9D%20token%20to%20avoid%20compatibility%20issues%3C%2FSTRONG%3E%20that%20may%20be%20caused%20by%20using%20the%20string%20%E2%80%9CEdge%2C%E2%80%9D%20which%20is%20used%20by%20the%20current%20version%20of%20Microsoft%20Edge%20based%20on%20EdgeHTML.%20The%20%E2%80%9CEdg%E2%80%9D%20token%20is%20also%20consistent%20with%20existing%20tokens%20used%20on%20iOS%20and%20Android.%20%3CSTRONG%3EWe%20recommend%20that%20developers%20use%20feature%20detection%20where%20possible%20and%20%3CFONT%20color%3D%22%23800080%22%3Eavoid%20browser%20version%20detection%20through%20the%20user%20agent%20string%3C%2FFONT%3E%2C%20as%20it%20results%20in%20more%20maintenance%20and%20fragile%20code.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1276068%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1276068%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%20it's%20the%20problem%20of%20the%20developers%20not%20using%20feature%20detection.%20Thank%20you%20for%20the%20information%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1276162%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%20sites%20detecting%20MS%20Edge%20as%20a%20Google%20Chrome%20browser%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1276162%22%20slang%3D%22en-US%22%3EAnytime!%3C%2FLINGO-BODY%3E
Contributor

Like others I find most of the browser detecting sites report that we are using a Google Chrome Browser that's really annoying. Now this is a problem. We love MS Edge and sites should also show what we are using! 

 

It hampers MS Edge popularity and market share statistics . 

I suggest that MS Edge team fix this. 

11 Replies

It actually is reporting edge in its user agent.

 

However, original edge used to say 'Edge' in its user agent, now its displaying 'Edg' instead, this is mainly because of compatibility; given all the standardizing issues with the legacy Edge, most sites would display older forms or simply refuse to support edge.

Those sites may have not been updated in years, so even if the problems with that browser were solved they'd still behave the same way.

 

To prevent this from happening edge is now reporting 'Edg'.

Newer sites should have no problems recognizing it as -the new- Microsoft Edge.

 

Older ones may think its an unsupported browser, but because edge also has Chrome in its user agent, they will identify it as Chrome compatible.

 

 

Checking and blocking based on user agents is not the best practice, and considering how user agents are being deprecated soon (i.e they will only be used to check between mobile/desktop devices, and for backwards compatibility the browser's version/name will stay 'frozen') this should not cause any problems.

 

 

 

@Thraetaona Sadly it seems most popular browser detecting sites have not been updated yet. Because they are still showing it as a Chrome browser. It's sad to see

Hmm, most show Edge to me.

But it really should not cause any problems, since user agents are soon getting deprecated anyway and the browser's name/version will stay frozen at a certain version.

So they won't stay a viable method to compare browsers' usages.
Hello,
Which channel/version are you using?
the user agent looks fine in 83.0.471.0
edge://version/

@HotCakeX dev 83.0.467.0

Which sites detect Edge by mistake?

@HotCakeX a quick google search "Check my browser name" tools reveal these

Those websites are most likely old and fail to detect the new Edge browser

looking at the browser string everything looks fine

edge://version/

 

 

4.png

 

1.png

 

2.png

 

3.png

 

 

Best Response
Solution

@HereItis 

 

Okay I actually found out why those websites are showing the incorrect browser:

  1. They are old.
  2. Those website developers haven't updated the code in their websites to detect the new Edge browser which has a different UA.

 

https://blogs.windows.com/msedgedev/2019/04/08/microsoft-edge-preview-channel-details/

 

 

User Agent String

 

With Microsoft Edge adopting Chromium, we are changing our user agent string to closely resemble that of the Chromium user agent string with the addition of the “Edg” token. If you’re blocking site access on user agent strings, please update your logic to treat this string as another Chromium-based browser.

Below is the user agent string for the latest Dev Channel build of Microsoft Edge:

 

 

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.48 Safari/537.36 Edg/74.1.96.24

 

 

We’ve selected the “Edg” token to avoid compatibility issues that may be caused by using the string “Edge,” which is used by the current version of Microsoft Edge based on EdgeHTML. The “Edg” token is also consistent with existing tokens used on iOS and Android. We recommend that developers use feature detection where possible and avoid browser version detection through the user agent string, as it results in more maintenance and fragile code.

 

 

 

@HotCakeX  it's the problem of the developers not using feature detection. Thank you for the information