Beside a sticky sidebar
The ordinary case: a content column next to a sticky nav.
Open →Embedded Help Center — test scenarios
Eleven fake storefront pages, each embedding
https://otyly-panie.resource-center-dev4.dev.tidio.pub a different way. Every page carries a
panel logging the rc-embed postMessage traffic, the frame count and
the parent hash. No build step: static files, drop them anywhere.
- The install
<script src="https://otyly-panie.resource-center-dev4.dev.tidio.pub/embed.js" defer></script>- That is all
- One tag, pasted where the Help Center should appear. The container in two of these scenarios is an escape hatch for themes that only allow a footer paste, never a step in the install.
Full page width, no menu
One wide column and nothing else. The plainest host page there is.
Open →Clamped to 32.5em
A theme’s rich-text width, ~520px. The known width trade-off.
Open →Pasted into the footer
What happens when the theme only offers a global code box.
Open →Container escape hatch
The fix for the above, and the only reason the container exists.
Open →The legacy async snippet
Back-compat for every copy already pasted on a customer site.
Open →Inside a hidden tab
Container is display:none at load, so the first height is zero.
Open →The snippet pasted twice
Two frames, each in its own place.
Open →A theme that fights back
Aggressive resets and an iframe rule. Isolation test.
Open →Alongside the merchant’s own widget
Their Tidio chat and our embed on one page. ADR-0022’s reason, made visible.
Open →Arriving on a deep link
Hash restore, plus the values that must be refused.
Open →