Changes between Version 1 and Version 2 of Ticket #3704, comment 5


Ignore:
Timestamp:
03/02/2016 12:11:42 PM (4 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3704, comment 5

    v1 v2  
    1 Sounds reasonable to me. But how would you (reliably) detect EdgeHTML other than by relying on the user agent string? The builds for Chrome, Opera and Edge will be compatible with all of these browsers. And we might have only one unified build in the future, anyway. Checking for the `chrome` namespace would allow to identify Chromium as of now. But since both, Edge and Firefox (Web Extensions), and who knows who else is following, expose the Chrome-like extension API with the `browser` namespace instead, this doesn't seem to be a good/reliable approach to detect the platform. Neither is there an extension API to detect the actual platform. So it seems the user agent string is all we got. 
     1Sounds reasonable to me. But how would you (reliably) detect EdgeHTML other than by relying on the user agent string? The builds for Chrome, Opera and Edge will be compatible with all of these browsers. And we might have only one unified build in the future, anyway. Checking for the `chrome` namespace would allow to identify Chromium as of now. But since both, Edge and Firefox (Web Extensions), and who knows who else is following, expose the Chrome-like extension API with the `browser` namespace instead, this doesn't seem to be a good/reliable approach to detect the platform. Neither is there an extension API to detect the actual platform. So it seems the UA string is all we got.