Two frontend features developers have been waiting for have finally reached Baseline 2026 status: CSS Anchor Positioning and the HTML Popover API. This means full support across all modern browsers — Chrome 125+, Firefox 147+, and Safari 26. And with it comes the end of JavaScript libraries like Floating UI, Popper.js, and Tippy.js for the vast majority of common use cases.
What is CSS Anchor Positioning?
CSS Anchor Positioning is a native browser mechanism that lets you position elements relative to other elements (called “anchors”) declaratively in CSS — without a single line of JavaScript. Previously, for a tooltip, dropdown, or floating label, you needed a JavaScript library to track element position in the DOM, calculate offsets, and recompute placement on scroll or resize.
Now the browser handles it natively:
.anchor { anchor-name: --my-anchor; }
.tooltip {
position: absolute;
position-anchor: --my-anchor;
bottom: calc(anchor(top) + 8px);
left: anchor(center);
}What Does the HTML Popover API Bring?
The Popover API solves the other half of the same problem — showing and hiding floating layers. Previously you needed JavaScript: event listeners, z-index management, Escape-to-close, click-outside dismissal, rendering into the correct page layer. Now plain HTML attributes do the job:
<button popovertarget="my-tooltip">Hover here</button>
<div id="my-tooltip" popover>Tooltip content</div>The browser automatically handles: correct rendering layer (top layer), Escape key dismissal, light-dismiss (clicking outside), proper focus management, and accessibility.
Why is Baseline 2026 an Important Milestone?
Reaching Baseline 2026 status means both features are implemented and stable across all major browsers. For developers this means practically: you can use them in production without fallbacks. No more @supports checks or polyfills needed for these specific features.
What Does This Mean for Your Projects?
For new projects in 2026, there’s no reason to reach for a JavaScript positioning library first. The combination of CSS Anchor Positioning and the Popover API covers the vast majority of use cases that previously drove Floating UI or Popper.js installs. The browser handles it faster, with less code, and with better default accessibility.
JavaScript for positioning still makes sense in edge cases: deeply nested menus with on-demand content loading, tooltips inside Shadow DOM with cross-origin limits, or virtualized lists where the anchor element may not be in the DOM. But these represent a fraction of typical positioning library use cases.
Practical Migration Tips
If you’re updating an existing project, we recommend a gradual approach: identify tooltips and dropdowns that don’t require on-demand content loading and migrate those first. Measure the results — less JavaScript typically means faster Time to Interactive and a smaller bundle size.
Conclusion
CSS Anchor Positioning and the Popover API are examples of the web platform maturing and reclaiming territory from JavaScript libraries. Reaching Baseline 2026 is a clear signal: if you’re not working with these features yet, start today. Your future self — and your users — will thank you for faster, lighter websites.
