Chrome 147: What Developers Should Know

Chrome 147 landed without big headlines, but there are a handful of changes worth knowing about.

What You'll Actually Use

Math.sumPrecise() — finally a native way to sum floating-point numbers accurately. Handy for financial calculations and data aggregation where 0.1 + 0.2 !== 0.3 was a real nuisance.

Container Timing API — you can now measure first-render timing for specific DOM blocks, not just the whole page. A solid tool for targeted performance optimization.

Autofill event — the browser fires an event before filling in a form. Gives you a hook to react to or control that moment.

SVG <textPath path="..."> — the path attribute can now be written inline, without a separate <defs> block and <path> element. Less markup.

CSS: Behavior Change

border-width, outline-width, and column-rule-width no longer auto-reset to zero when style: none/hidden is set. Computed styles are now more predictable and aligned with Firefox/WebKit.

Security

Local Network Access protection has been tightened — WebSocket connections and navigation to local network addresses are now restricted. Some users are being moved to HTTPS-by-default.

Device Memory API is intentionally less precise now, to reduce fingerprinting surface.

Removed

Inline XSLT for SVG — deprecated and removed.

Takeaway

Chrome 147 is about performance, accuracy, and security. No revolutions, but Math.sumPrecise() and Container Timing API are worth keeping in your toolkit.