![]() If you’re blocking site access on user agent strings, please update your logic to treat this string as another Chromium-based browser.īelow is the user agent string for the latest Dev Channel build of Microsoft Edge: 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. Those website developers haven't updated the code in their websites to detect the new Edge browser which has a different UA. ![]() ![]() 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 I actually found out why those websites are showing the incorrect browser: 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.Ĭhecking and blocking based on user agents is not the best practice, and considering how user agents are being deprecated soon (i. Newer sites should have no problems recognizing it as -the new- Microsoft Edge. To prevent this from happening edge is now reporting 'Edg'. 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. 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. It actually is reporting edge in its user agent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |