Aaron nailed it. We’re still stuck on 2025-07 six months later with no viable path forward.
The decision to remove position:absolute because of “inappropriate use” goes against what the web platform is fundamentally about. The web is open by design. Developers should be free to build creative, differentiated experiences - even messy ones. The more constraints you impose, the less room there is for innovation, and eventually every app ends up looking and working exactly the same. At that point, what’s the value of extensibility?
Merchants - especially Plus merchants - are paying serious money to extend their checkouts. We can’t go back to them and say “the UI extension that’s been working great for years now needs to look worse because of a platform update”. Updates should make things better and more open over time, not take capabilities away.
I understand the desire to prevent misuse, but the right approach is documentation and guidance - not removing core web primitives. position:absolute isn’t some dangerous hack, it’s a fundamental CSS property that every web developer relies on.
We need position support back, or at the very least an honest acknowledgment that checkout extensions are now more limited than they were a year ago.