News

U.S. DOJ renews push for Google to sell Chrome

However, the Justice Department seems to be easing off a push to sell Android

Google Chrome on a MacBook

The U.S. Department of Justice (DOJ) is pushing to have Google sell off its web browser, Chrome.

In a court filing submitted on March 7, the DOJ reiterated demands that the court break Google up with a focus on making the search giant divest the Chrome browser. Chrome is the most popular web browser in the world, and its underlying technology powers many other browsers, including Microsoft’s Edge, Brave, Vivaldi and more.

The filing is the latest development in a long-running legal battle between the Justice Department and Google over its search monopoly. In August 2024, U.S. Judge Amit P. Mehta ruled that Google maintained a monopoly in online search. In the months since, the DOJ has submitted arguments to Mehta on how to address the Google search monopoly. Selling Chrome was one idea, and this latest filing doubles down on that.

If the DOJ did force Google to sell Chrome, it would have wide-ranging repercussions given the browser’s dominant position both among users and as the power behind many competing browsers.

Separately, the DOJ sued Google over its alleged monopoly in advertising tech, which is still awaiting a ruling. Canada’s Competition Bureau launched its own lawsuit against Google for anti-competitive conduct in digital ads last year.

One of the Justice Department’s main concerns with Chrome is how Google uses it to push people to its search product. Forcing Google to sell Chrome would “permanently stop Google’s control of this critical search access point,” the DOJ argued.

Selling Chrome isn’t the only change the DOJ wants. The filing also seeks to ban Google from paying companies to make its search engine the default option, claiming this practice allows Google to maintain an illegal monopoly in online search.

Currently, Google pays Apple and Mozilla, the maker of Firefox, to make Google search the default option on their respective devices and software. Moreover, Google makes deals with Android smartphone manufacturers to use Chrome as the default browser and to feature Google search products.

The idea here seems to be that banning Google from paying for default status would open up competition for search engines to earn that place on merit. However, it could just open the field for another search engine operator with deep pockets — for example, Microsoft, which owns Bing — to buy its way into dominance.

DOJ changes course on AI, Android

While the DOJ pushes ahead on some ideas, it’s pulling back on other suggested solutions. In the March 7 filing, the Justice Department changed tact regarding Google’s artificial intelligence (AI) investments. Instead of attempting to stop Google from investing in AI, the DOJ now wants to Google to notify government officials before making investments in the tech.

Similarly, the DOJ pulled back on making Google divest of Android, a smartphone operating system (OS) that powers billions of devices worldwide. In the filing, the Justice Department argued that Google should have to make changes to its Android business practices, seemingly ending a push for Google to divest from the OS.

Google, unsurprisingly, opposes these measures and in its own filing to Mehta, it argued for a narrower approach. The search giant wants to be allowed to continue paying for default placement but with new rules about how restrictive the agreements can be.

The company has argued its search deals didn’t break the law and repeatedly claims that people choose Google search because it’s better than rival search engines. However, Google search has increasingly faced criticism for decreased quality, especially in recent months as Google integrated more AI features.

Source: New York Times, Android Authority

MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.

Related Articles

Fatal error: Uncaught Aws\S3\Exception\PermanentRedirectException: Encountered a permanent redirect while requesting https://ms-staging-baselayer-static-assets.s3.ca-central-1.amazonaws.com/?list-type=2&delimiter=%2F&prefix=uploads%2Fwpcf7_uploads%2F. Are you sure you are using the correct region for this bucket? in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php:49 Stack trace: #0 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(209): Aws\S3\PermanentRedirectMiddleware->Aws\S3\{closure}(Object(Aws\Result)) #1 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(Aws\Result), NULL) #2 /var/www/html/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() #3 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(163): GuzzleHttp\Promise\TaskQueue->run() #4 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(189): GuzzleHttp\Handler\CurlMultiHandler->tick() #5 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Handler\CurlMultiHandler->execute(true) #6 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn() #7 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #8 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #9 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #10 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #11 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending() #12 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClientTrait.php(58): GuzzleHttp\Promise\Promise->wait() #13 /var/www/html/vendor/aws/aws-sdk-php/src/ResultPaginator.php(151): Aws\AwsClient->execute(Object(Aws\Command)) #14 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(52): Aws\ResultPaginator->valid() #15 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(69): Aws\map(Object(Aws\ResultPaginator), Object(Closure)) #16 [internal function]: Aws\flatmap(Object(Aws\ResultPaginator), Object(Closure)) #17 /var/www/html/wp-content/plugins/s3-uploads/inc/class-stream-wrapper.php(695): Generator->valid() #18 [internal function]: S3_Uploads\Stream_Wrapper->dir_readdir() #19 /var/www/html/wp-content/plugins/contact-form-7/includes/file.php(362): readdir(Resource id #734) #20 /var/www/html/wp-includes/class-wp-hook.php(322): wpcf7_cleanup_upload_files() #21 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #22 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #23 /var/www/html/wp-includes/load.php(1280): do_action('shutdown') #24 [internal function]: shutdown_action_hook() #25 {main} thrown in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php on line 49