Forum Discussion
google is incompetent
Update 2:
"The stated explanation behind the original warning was that Chrome didn't realize that MSEdge maintained the ability to revoke extensions later discovered to be malicious. They didn't realize this because MSEdge does not hit Google's SafeBrowsing service for revocation information, but instead queries Microsoft's servers, which cache revocation information retrieved directly from SafeBrowsing."
Update 2:
"The stated explanation behind the original warning was that Chrome didn't realize that MSEdge maintained the ability to revoke extensions later discovered to be malicious. They didn't realize this because MSEdge does not hit Google's SafeBrowsing service for revocation information, but instead queries Microsoft's servers, which cache revocation information retrieved directly from SafeBrowsing."