Google says ChromeOS will keep receiving regular updates and security patches through mid-2034, after which qualifying newer Chromebooks will be able to migrate to the new Googlebook OS. 9to5Google reports: Starting with Chromebook updates, Google says that "Chromebooks you have today will continue to receive updates through their supported lifetime," with all Enterprise and Education management capabilities remaining in place as well: "We will maintain support for current Chromebook devices running ChromeOS as outlined in our Auto Update policy and the Chromebooks you have today will continue to receive updates through their supported lifetime..." Google adds that similar management tools will be coming to Googlebook, but they're not available yet. Apparently they're planned for the second half of 2027. Meanwhile, Google says that "many" existing Chromebook models will be eligible to transition from ChromeOS to Googlebook OS. More details are coming "soon." A later note specifies that Google is referring to "newer commercial Chromebook models." Notably, Google specifies a year when ChromeOS updates will come to an end in a later note -- 2034. Chromebooks with a 10-year update policy that extends past 2034 will be eligible to move to Googlebook OS. [...] Finally, in regards to apps, Google says that it is "committed" to web developers despite an increased focus on Android apps on Googlebooks.

Read more of this story at Slashdot.

"Google should be required to divest the Chrome browser, and prohibited from paying Apple to distribute Google's search engine, the nonprofit advocacy group Public Knowledge argues in a new court filing," MediaPost reports, citing a friend-of-the-court brief filed Tuesday in the D.C. Circuit Court of Appeals: The group adds that "independent ownership" of Chrome "would open the distribution channel Google controls and allow Chrome to serve browser users when it makes privacy decisions and determines how to integrate search and (artificial intelligence)..." In September 2025, [U.S. District Court Judge] Mehta issued a remedies order that requires Google to share some data about users' searches with "qualified" competitors and to provide syndicated search results and ads to those competitors. The order also prohibits Google from entering into exclusive distribution contracts for Google Search, Chrome, Google Assistant and the Gemini app for six years, but allows the company to continue to make payments for search-ad revenue or distribution to Apple, Mozilla and others... Google recently appealed Mehta's order. The company argued in its written brief that it "prevailed in the marketplace fair and square," adding that Apple and Mozilla "sensibly chose" Google as the default search engine "because it gave their users the best experience," and because Apple and Mozilla would earn the most ad revenue through the deals. The [U.S.] Justice Department and states countered to the appellate court last week that the liability finding should stand, and also argued that Google should have been banned from paying Apple and Mozilla for placement as the default search engine on their browsers. [Antitrust enforcers had originally asked the judge to order Google to divest Chrome, but he's already rejected that request.] The government did not argue in its appellate papers that Google should be forced to sell Chrome. But Public Knowledge independently contends in its friend-of-the-court brief that divestiture would benefit consumers... "Divestiture would place those decisions with an institution whose success depends on serving browser users primarily...." The group is calling the appellate court's attention to Google's April 2025 decision to preserve tracking cookies — a reversal from its earlier plans to block third-party cookies by default. "Google is in the position of both deciding Chrome's tracking rules while running the advertising business affected by them," Public Knowledge writes. "An independent Chrome could make those decisions on behalf of users alone." But Firefox developer Mozilla filed its own friend-of-the-court brief Thursday warning Firefox could be forced to "exit the browser and browser engine markets" if it can't receive payment from Google for distributing its search engine, according to a later report from MediaPost: Federal and state antitrust enforcers recently asked the appellate court to reverse the portion of Mehta's order that allows those payments to continue. But Mozilla counters in its new friend-of-the-court brief that Mehta's decision regarding those payments was supported by the evidence --including a study it conducted concluding that its revenue would "decline dramatically" if forced to replace Google with Bing as Firefox's default search engine... Google is expected to file new arguments with the appellate court next month.

Read more of this story at Slashdot.

Google says AI-assisted workflows helped Chrome fix 1,072 security bugs across versions 149 and 150, more than the previous 23 releases combined. The company is also testing twice-weekly security updates and "dynamic patching," which could apply most fixes without requiring users to restart the entire browser. "By leveraging Chrome's multi-process architecture, dynamic patching sequentially replaces background child processes (like the Renderer and GPU) with updated binaries on the fly," says Google in a blog post. PiunikaWeb reports: Alongside dynamic patching, Google is rolling out smarter background updates during periods of minimal user disruption. Starting with Chrome 150 on macOS, the browser takes advantage of the operating system's windowless state. If all Chrome windows are closed but the app remains running in the background, the browser will quietly auto-restart to apply pending updates. For enterprise environments, IT admins can continue to manage fleet-wide deployments through Chrome Enterprise Core or enforce update prompts using the RelaunchNotification policy. Google's long-term vision is a browser that remains continuously protected in the background without interrupting your daily browsing session. In the meantime, you can manually trigger pending updates by clicking the update prompt in the top-right corner of Chrome.

Read more of this story at Slashdot.