Chromium Services & Features disabled in new Edge
This post takes a look at the following:
List of services replaced or turned off in Chromium-based EdgeExample of a replaced Chromium ServiceThe key area of focus for Microsoft Edge
This situation is just like Chrome. Google expects Chrome users to use only Google Services. The same way, Edge users are supposed to be only communicating with Microsoft Services. The development team has identified such 50+ services and have been either turned off or replaced. It seems to be a necessary step to avoid conflicts. Below is the list of services removed:
Safe browsingNearby messagesLink DoctorAd blockingUser data syncSpellcheckSuggestTranslateSmartLockForm FillPush NotificationsWeb StoreExtension StoreMaps GeolocationGoogle NowSpeech inputGoogle PayDrive APIChrome OS hardware idDevice registrationGoogle Maps Time zoneGoogle Cloud StorageCloud PrintGoogle DNSSupervised ProfilesAddress FormatNetwork LocationNetwork TimeFavicon serviceGoogle Cloud MessagingSingle sign-on (Gaia)Content Hash FetcherFlighting ServiceComponent Updater ServiceRAPPORT serviceChrome OS monitor calibrationChrome OS device managementAndroid app password syncOffline Page ServiceFeedbackDomain Reliability MonitoringData Reduction ProxyChrome CleanupDeveloper Tools Remote DebuggingiOS Promotion ServiceOne Google Bar DownloadBrand Code Configuration FetcherWebRTC LoggingCaptive Portal Service
Example of replacement of Chromium Service
Microsoft has explained it in their slideshow how they did the changes with “Identity and Single Sign-On” Edge is expected to support Single-Sign-on with Microsoft Accounts (MSA) or Azure Active Directory (AAD). However, the architecture or Chromium is different from Edge. I am sure this will have an impact on Plugins which depend on Google Services. Either they will have to come up with the modified version or let it go. We will get to know that with time.
We use a client SDK, called OneAuth, that handles most everything for us: login UI, all types of SSO, MSA and AAD, etc.We modified the Sign-in flow by invoking EdgeAuthenticationManager in SigninViewController::ShowSignInAnd to handle cases where the browser needs to make an authenticated service call, we specialized the OAuth2AccessTokenFetcher class: EdgeAccessTokenFetcherImpl
OneAuth takes care of the rest!
Key Area of Focus for Microsoft Edge:
As of now, the Chromium-based edge is focusing on these areas. Battery life is one of the critical areas. I can only hope Edge doesn’t take a toll on performance and battery as Chrome.
AccessibilityEditingSecurityARM64FontsToolingAuthenticationLayoutTouchBattery lifeScrollingWeb Standards
Apart from these, Edge comes with PlayReady DRM, Services integration and Single Sign-On. Play Read DRM makes it possible to stream secure content, i.e., DRM from services like Netflix, enables hardware decryption, supports LPAC and power savings. It is also Widevine ready. Source: @TheWalkingCat.
