Do you mean that they advertised for Chrome on their properties? Advertising on your own property is legitimate in my book. And simple advertising isn't a "dark pattern".
Or do you mean something else?
And advertising something on your own property sure sounds reasonable, but I think it's a slightly different story when "your own property" is "the de facto homepage of the internet". That's what I meant by "abusing monopoly position".
Maybe as someone with above-average technical ability this looks obvious to you. To a lot of people, it isn't. And this pattern is aimed at fooling the less technically literate.
For example, signing into a Google site from Chrome also signs you into the browser; it's unclear how this happens, what personal information it compromises, and more than that it's an unexpected and unwelcome surprise when it happens.
Clearing Google cookies in Chrome also doesn't work, for related reasons. Try deleting all cookies in Chrome the immediately refreshing the list: Google cookies immediately re-appear.
It's not that these things are necessarily actually dangerous. But the blurring of the line between service and user agent scares me.
They eventually created an option to disable that behaviour after a lot of user complaints:
"While we think sign-in consistency will help many of our users, we’re adding a control that allows users to turn off linking web-based sign-in with browser-based sign-in—that way users have more control over their experience. For users that disable this feature, signing into a Google website will not sign them into Chrome."
https://www.blog.google/products/chrome/product-updates-base...
The most interesting part in all this is that the Adobe Flash you just downloaded and installed is not even used by Chrome, which ships its own.
So much so that many many people I know that worked on helpdesk;s at the time where getting lots of complaints about "the internet is missing" meaning their Icons changed from the IE logo to the Chrome logo because chrome was changed to the default browser with out them understanding what happened.
Add to the fact that Chrome would also install in AppData to avoid having to have Admin rights to install so it could be install on corporate/enterprise systems by normal users...
Another example: Windows: Chrome, installation being under user profile to bypass any system checks during installation process itself and further updates.
It is ostensibly for security and benefits developers because of less fragmentation. But it actually hurts users in the long run because of the centralizing effect. It also enables chrome to sneak in features that users wouldn't necessarily accept.