Microsoft delivered an update for the same vulnerabilities on Jan. The first Chrome security update issued after Edge's Jan. The shorter the lag, the better: Criminals could conceivably exploit a large gap by reverse engineering Chrome's fixes for that version's security vulnerabilities, then applying the results to a not-yet-patched Edge. One question that Microsoft has not addressed is how long it would take to get from Chromium to a finished version of Edge, most importantly whether there would be a lag, and if so, how long,between Google launching Chrome and Microsoft releasing Edge. Please provide any feedback you may have on this.Since then, developers at both Google and Microsoft have been working on their versions of Chromium 80, each using a multi-stage cadence of Canary, Dev, Beta and then Stable builds to release progressively more reliable and polished code. I am not sure how to read this and what is that 8.4.1 is not supported in Chromium that Google Chrome can support. Note#5 “Microsoft Edge Chromium has been tested on the following versions of Pega Platform:Ĭhromium supported from 8.4.3 and beyond, even though it states it support 8.3 from version 8.3.4 and beyond seems it doesn't include all the versions 8.4.

We found below information from the documentation ( ) which doesn't provide confidence and not sure what functionality we would miss compared to Google Chrome (our current default browser). We would like to understand whether this Pega platform version 8.4.1 is fully compatible with Edge Chromium. We are planning to use Edge Chromium as a standard browser across the Organization and we will be deploying apps in Pega platform 8.4.1. Pega Robotic Automation Release and Build Notes

Chrome edge