A "vintage" CSS bug from 2017 just got revived by React, Next.js, Webflow, and every modern starter template that resets overflow-x: hidden on the body to stop horizontal scroll. The sticky element itself looks fine in DevTools. The 2026 Chromium tracker just merged a patch about it (issue #481019005). Reddit is full of dev threads from the last 60 days asking why their sticky won't pin. StickyPunk is the deterministic two-minute fix.
overflow: hidden creates one. Including the wrapper four levels up.When you write position: sticky on an element, the browser walks UP the DOM to find the nearest "scroll container" and pins the sticky to that container's viewport. Any ancestor with overflow: hidden, auto, or scroll creates one of those scroll containers, whether you wanted one or not. If that scroll container is the same height as the sticky element itself — which it usually is on a layout grid wrapper — the sticky has nothing to scroll past, so it never activates. DevTools doesn't surface this because the sticky element looks correct. Your only signal is "it doesn't pin."
overflow: hidden they didn't know they had set · informal sample, June 2026position: sticky shipped in Safari and was declared a "solved problem" · narrator: it wasn'toverflow: clip hit baseline support in every modern browser — the fix nobody knows about · CSS Overflow Module L3hidden → clip. Same visual result. Sticky lives. · git-reversiblePLAIN ENGLISH overflow: hidden means "crop content AND make this a scroll container." overflow: clip means "just crop content, leave the scroll context alone." When the W3C added clip in CSS Overflow Module Level 3, they specifically called out that it's the fix for sticky-positioning collisions — but nobody's framework reset has switched over yet. Tailwind's overflow-hidden utility still emits the broken version. Bootstrap's .overflow-hidden still emits the broken version. Webflow's layout wrappers still emit the broken version. That's the whole pitch.
Paste the part of your page that contains the sticky element and the layout wrappers above it. We render it in a sandboxed iframe inside your browser, walk every position: sticky element up its ancestor chain, and flag the exact <div> that's strangling it. Zero upload, zero storage, zero AI. Pure DOM traversal + window.getComputedStyle(). How it works ↓
Your pasted HTML loads into a hidden, script-disabled iframe inside your own browser tab. Nothing leaves the page. The iframe is throwaway — destroyed the moment the audit completes.
For every element where getComputedStyle(el).position === 'sticky', we climb el.parentElement all the way to <html>, checking each ancestor's overflow, overflow-x, and overflow-y as we go.
For each strangling ancestor we find, you get the exact selector, the depth in the chain, and the deterministic patch: overflow: hidden → overflow: clip. Copy button included. Git-reversible. Old browsers see exactly what they used to.
StickyPunk is the second product in the Punk Store. PalettePunk is live now — the Display P3 / OKLab color audit that scored Apple, Figma, YouTube, and Google all at 40/100. AutoPunk (CSS interpolate-size patch for height transitions) ships next month. Three more in the queue this quarter. The Punk Pass gets you all of them — current and future — for the price of buying two separately.
No subscription. No login wall. No "contact sales." Buy once, own forever, use on every project you ever ship.
Yes. Nothing uploads. The pasted HTML loads into a sandboxed iframe inside your tab. No fetch, no XHR, no telemetry. View source on this page if you want to verify — the whole scanner is in /scan.js, which is <400 lines of vanilla JS with zero dependencies.
Sometimes overflow: hidden is deliberate — sliders, carousels, content that needs to clip and not scroll. The auditor surfaces those separately as "REVIEW" findings, not "DEAD." If the strangler is intentional, ignore that finding. Standalone-purchase customers get an "Ignore this selector" feature for repeated false positives in the project-wide auditor.
overflow: clip instead of overflow: visible?Because visible stops clipping the content. If you had overflow: hidden on a wrapper to prevent horizontal scroll caused by a 110vw element inside it, switching to visible would re-expose the scroll. clip still crops the overflow — but without creating a scroll container. That's the W3C-spec-sanctioned fix: same visual result, no sticky-killing side effect.
overflow: clip?Chrome 90+ (April 2021), Firefox 81+ (September 2020), Safari 16.4+ (March 2023). Baseline since March 2023. Over 95% of global users per caniuse as of June 2026.
Yes. Same Radio Art LLC, same engineering, same lifetime-license model, same "we publish the methodology" doctrine. If you bought PalettePunk, the Punk Pass upgrade puts you ahead $99 the moment StickyPunk ships.
The browser-side scanner you're running right now is the whole methodology. View source. The project-wide auditor adds (a) a directory walker that parses your component tree, (b) framework-specific rules for Tailwind/Bootstrap/Webflow utility classes, and (c) the CI plugin. Same core logic.