You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that there are several differences between these two, and also that Legacy Edge is not supported from V15+ on, a isLegacyEdge() method could be created so that isEdge() would be deprecated and simply call isLegacyEdge and a new isChromiumEdge() could be created, this last one searching for the new user agent feature Edg/
The text was updated successfully, but these errors were encountered:
My understanding is that intent of Microsoft with the new user agent has been, that new Edge is supposed to be treaded as Chrome, as it based on same engine.
The current isEdge method VBrowserDetails.isEdge() (and consequently its server side sibling) is meaning that the Browser is the EdgeHtml legacy browser. Vaadin component internal implementations use this to do things differently as EdgeHtml does not support some things Chrome does.
Thus what is needed is to clarify this in the documentation. This is the first step.
Another matter is the possible API additions to further clarify the case
As proposed method isLegacyEdge() as alias to isEdge() is more intuitive.
isChrome() should be still true for both Chrome and Chromium based Edge.
isChromiumEdge() would then be a new method returning true if Browser is Edge variant of Chrome (as it is stated by user agent)
According to https://blogs.windows.com/msedgedev/2019/04/08/microsoft-edge-preview-channel-details/ , chapter "User Agent String", Chromium Edge's user agent is now Edg/ instead of the Legacy Edge's edge/.
Given that there are several differences between these two, and also that Legacy Edge is not supported from V15+ on, a isLegacyEdge() method could be created so that isEdge() would be deprecated and simply call isLegacyEdge and a new isChromiumEdge() could be created, this last one searching for the new user agent feature Edg/
The text was updated successfully, but these errors were encountered: