Chrome 158 brings WebHID to Android, no API changes needed
Sites that already use WebHID on desktop, for mechanical keyboards, gamepads and headset controls, now work on Android 17 and later with the same code.
Tagged
Sites that already use WebHID on desktop, for mechanical keyboards, gamepads and headset controls, now work on Android 17 and later with the same code.
All six critical bugs are memory-safety flaws, in WebView, the GPU component, Media, garbage collection, ANGLE and WebAudio. None are confirmed exploited yet.
A hijacked element picker let any website register a trusted filter and run arbitrary JavaScript on other sites, with one click. The fix landed in 1.75.4.
navigator.install() lets a site trigger a web app install, including cross-origin, replacing a non-standard event every PWA builder had to special-case.
WebKit guidance for the new square display warns against fixed headers, oversized modals, and trusting the user agent string to detect the device.
Chrome, Firefox and Edge now back the same set of skills that teach coding agents web platform best practices, and version 1.0 adds a scan for outdated patterns in existing code.
Firefox 160, out on 10 November, supports the Web Speech API SpeechRecognition interface on desktop, converting speech to text in 40 languages entirely on-device.
CVE-2026-125350, a use-after-free in XML handling, is being exploited in the wild. It is the eighth Chrome zero-day Google has confirmed under active attack this year.
exportKeyingMaterial() now requires a context argument, and two non-standard datagram properties are gone, alongside new support for custom CONNECT headers.
XSLTProcessor and the XML stylesheet processing instruction stop working in Stable on 17 November. Chrome says XSLT shows up in just 0.02% of page loads.
A Chrome 155 enterprise policy change made the chrome.debugger API fail all-or-nothing instead of per-site. Google rolled it back on 3 November.
A new corner property, and per-corner variants like corner-top-left, set border-radius and corner-shape together in one declaration instead of two.
Sekoia traces a watering-hole campaign, linked to the Russian group APT29 with moderate to high confidence, that hijacked a popular analytics script to serve two-year-old Safari and Chrome exploits to visitors.
The stable channel update fixes flaws in Dawn, Prerender and ANGLE among others. Google has not flagged any of them as exploited, but the sheer count is worth a prompt update.
WebKit now automatically rewrites light-themed sites into dark mode for users who want it, preserving contrast and letting developers opt out with one CSS declaration.
The property finally takes a custom string instead of the default ellipsis when text is clipped, something Firefox has supported since 2011.
The 27 October stable update fixes four critical bugs, including a FileSystem flaw that can let an attacker break out of the browser sandbox.
A new opt-in API lets sites and extensions call local, on-device models for text generation, classification and embeddings, no API key or server required.
Mozilla's MFSA 2026-118 lists at least 144 individual CVEs for Firefox 159, continuing a disclosure change that stopped bundling internal memory-safety bugs into one catch-all ID. None is flagged as exploited in the wild.
Chrome drops emSign ECC Root CA - G3 from its trust store on 27 October after eMudhra intermediate keys turned out to be forgeable. Sites chaining to it need a new certificate now.
WebKit's release also adds a ::field-content pseudo-element for Customizable Select, and renames the Grid Lanes flow-tolerance property to fit-tolerance.
Firefox was the last major browser holding this behind a flag. With 159 out, animation-timeline works without JavaScript everywhere that matters.
WebKit adds the device-posture media query and a Viewport Segments API behind feature flags, letting web pages detect and lay out around a fold for the first time.
The stable release patches memory-safety bugs in CSS, Paint, WebRTC, Skia and Accessibility. Google says none are exploited in the wild.
Eight eMudhra intermediate certificates had compromised private keys. Mozilla blocked them in hours, then shipped Firefox 158.0.1 and NSS 3.131.1 to cover everyone else.
WebKit blocked network access to the invisible third-party services that turn a login email into a permanent, cross-site tracking ID, live now in iOS, iPadOS, macOS and visionOS 27.
The random() function generates a number directly inside a property value and can share results across elements and properties. Chrome is the first browser to support it.
Leo chats with Brave's open-weight GLM 5.3 Flash model are now encrypted from the browser to a verified secure enclave, so neither Brave nor the model host can read them.
A Work mode lets ChatGPT send messages, fill forms, download files and group tabs across your browser, not just read them. It replaces the computer-use reach OpenAI lost when it shut down Atlas.
Chrome 155.0.8059.84/.85 fixes ten security bugs, including a critical use-after-free in Prerender. No sign of in-the-wild exploitation yet.
Security firm XBOW paired researchers with OpenAI's GPT-5.6 Sol to chain three Chrome bugs into a working exploit in six days, earning a bounty for a flaw Google says reaches about a billion users.
Mozilla has also stopped bundling internally found memory-safety bugs into one catch-all CVE, so this release shows each flaw as its own advisory entry.
Dividing two CSS values of the same type now returns a plain unitless number in Firefox too, matching Chrome and Safari, which already shipped it.
WebKit has started shipping interpolate-size and calc-size(), the CSS pair that lets you animate height: auto without JavaScript, two years after Chrome did.
The stable release patches 247 vulnerabilities, including four critical use-after-free bugs; an Anthropic researcher used Claude to help find two of them.
The with { type: "text" } import attribute, a Stage 3 TC39 proposal already supported in Deno and Bun, ships in Chrome's stable channel from 6 October.
Chrome 155 decodes .jxl images without a flag, using a new Rust-based decoder. Firefox is due to follow on 13 October, and Safari has supported the format since 2023.
A block of JSON tells the browser which links to prerender. On a server-rendered site it closes most of the perceived gap with a single-page app.
Baseline turns "which browsers support this" into a yes or a no, and it is now built into MDN, the docs, and a linter you can run in CI.
Bare module specifiers work natively in every current browser. For a site with a handful of dependencies, that removes the build step entirely.