I would imagine it's regulatory capture by accident - Chrome constantly gets requests from developers (which includes big corporations) to add features, so I im

I would imagine it's regulatory capture by accident - Chrome constantly gets requests from developers (which includes big corporations) to add features, so I imagine saying 'no' requires a lot of user research to back up why users/developers actually don't want a feature.