Urgent.News

What's breaking now, across thousands of outlets.

Tech

Chrome cookies: why google.com survives 'delete on close', again

If you set Chrome to delete site data when you close all windows, Chrome 152 still keeps google.com's cookies, local storage and session storage. Jeff Johnson, the Mac developer behind Lapcat Software, reproduced it on two Macs on September 5, 2026, and a Hacker News user reproduced it in open-source Chromium the same day. The same developer found the same kind of exemption for Google's sites in…

If you enable Chrome to delete site data when you close all windows, the browser retains google.com's cookies, local storage, and session storage. Jeff Johnson, a Mac developer, discovered this issue on two Macs in September 2026, while a Hacker News user confirmed it in open-source Chromium on the same day. Google had previously fixed a similar issue in 2020.

This behavior contradicts the intended function of the delete site data on close setting, which is supposed to clear all site data when the last window is closed. The only site exempted from this behavior is www.google.com. The issue persists in Chromium 152.0.7977.75 on Debian, indicating that it is part of the shared code rather than specific to Google's branded build.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

ICANN and Verisign: why 22,000 .name domains will be deleted

ICANN has approved a request from Verisign to delete every third-level .name domain, addresses like john.doe.name , about 22,000 of them, including registrations paid for until 2040.

  • ICANN approves Verisign's plan to delete 22,000 .name domains
  • Domains to be erased after 90-day notice period starting Feb 2027
  • Concern over domain loss and potential email address recovery

Plugin4Shell Hit 26,000 Agents Before Anyone Noticed. Your Coding Agent’s Plugin Store Is the New npm.

A zero-click RCE vulnerability across Claude Code, Codex, Copilot, and Gemini CLI proves that AI coding agent plugin marketplaces have inherited every supply chain attack pattern from package…

  • Over 26,000 AI coding agents affected by Plugin4Shell vulnerability before May 2026
  • Exploit exploits SHA-pinned commit handling, allowing attackers to deploy malicious branches
  • Highlights need for improved security in AI coding agent plugin marketplaces

More from Sunday 27 September →