The CSS Anchor Positioning spec landed in Safari 27 last week. Suddenly your legacy position: absolute elements — the ones that worked perfectly for a decade — are accidentally tethering to anchor-name declarations elsewhere in the same subtree. Your badge teleports to the tooltip target. Your absolute close-button vanishes off-screen. Your "10% off" tag ends up on top of the price. The spec changed underneath you, and the WebKit team panicked so hard they shipped position-anchor: none as an explicit opt-out 48 hours after the implicit-default behavior caused production fires across the web. AnchorPunk finds every absolute element at risk and emits the opt-out for it.
position: absolute resolves its coordinates. Your 2014 code does not know that.For 25 years position: absolute resolved to the nearest positioned ancestor's containing block. Simple. Deterministic. Then CSS Anchor Positioning landed and introduced a new behavior: out-of-flow elements can be tethered to any element on the page that declares anchor-name. Some browser implementations apply an implicit-default-anchor when one is available in the ancestor tree, which means your absolute close-button suddenly tethers to a tooltip the designer added to the header six months ago, which puts your button at the wrong corner of the wrong card. The WebKit team realized within days that this would break legacy codebases at scale, so they shipped position-anchor: none in Safari 27 as an explicit opt-out. Most developers haven't heard of this property yet. AnchorPunk scans your DOM for at-risk absolutes and emits the opt-out for every one of them.
position: absolute in complex codebases — anyone whose Safari just updated is now sitting on a ghost-tether time bomb · est. CSS-in-active-use devsposition-anchor: none as the opt-out. That's how panicked they were. · WebKit changelog June 2026position-anchor: none per at-risk element fixes every ghost-tether. Browsers that don't support the property ignore it. · spec-sanctioned opt-outPLAIN ENGLISH The CSS spec for absolute positioning quietly changed last week. If you have any position: absolute elements in a codebase that also uses anchor-name anywhere — and you use Tailwind, shadcn/ui, Radix, Headless UI, or basically any modern component library, you do — those absolutes may now be tethering to anchors you didn't write. Your UI looked perfect last Tuesday and looks broken today, and the developer has no idea what changed because they didn't change anything. AnchorPunk walks your DOM, finds every out-of-flow element at risk, and emits the one-line opt-out property the WebKit team shipped specifically to save you from this trap. Pure additive enhancement. Browsers that don't know about it ignore the line. Browsers that do know about it stop tethering.
Paste any chunk of your page that has position: absolute elements — cards with badges, dropdowns with tooltips, modals, popovers, anything where you pin a child to a parent. We render it in a sandboxed iframe inside your browser, walk every absolute and fixed element, check its position-anchor computed value, and detect any anchor-name declarations in the same subtree. Zero upload, zero storage, zero AI. Pure DOM traversal with spec-aware logic.
Your pasted HTML loads into a hidden, script-disabled iframe inside your browser tab. Nothing leaves the page. The iframe is destroyed the moment the audit completes.
For every element where getComputedStyle(el).position is absolute or fixed, we check its position-anchor computed value AND walk its ancestor chain looking for any element with anchor-name declared. We also build a global map of every anchor-name in the document.
For each element with an explicit position-anchor (TETHERED) or with anchor-name ancestors (REVIEW), we emit a one-line rule: position-anchor: none; scoped to that selector. Copy button included. Git-reversible. Browsers that don't support the property ignore the line; browsers that do stop tethering.
AnchorPunk is the fifth product in the Punk Store. PalettePunk audits color. StickyPunk finds sticky-positioning failures. KeyboardPunk fixes mobile inputs the iOS keyboard hides. SelectPunk catches Firefox-broken dropdowns. Five products today. Six more shipping this quarter. The Punk Pass gets you all of them — current and future — for less than the cost of buying three separately.
No subscription. No login wall. No "contact sales." Buy once, own forever, use on every project you ever ship.
position-anchor: none per at-risk element, all git-reversibleCSS Anchor Positioning Module Level 1. The position-anchor property and anchor-name declaration are the new pieces. Safari 27 shipped both in June 2026; Chrome 149 shipped at the same time; Firefox is implementing.
Yes. Nothing uploads. The pasted HTML loads into a sandboxed iframe inside your tab. We walk the DOM using standard getComputedStyle() queries. View source — the scanner is in /scan.js, vanilla JS, zero dependencies.
Then ignore the finding — or set position-anchor to the specific anchor-name you meant. The bug isn't that tethering exists; it's that implicit tethering is unpredictable across browsers. Being explicit always wins.
No. position-anchor: none is an unknown property to browsers that don't support CSS Anchor Positioning, and unknown properties are silently ignored. Pure additive enhancement.
Yes. Same Radio Art LLC, same engineering, same lifetime-license model. Punk Pass pays for itself by your second Punk.