<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iframe on Kliku Kliku</title><link>https://klikukliku.dev/tags/iframe/</link><description>Recent content in Iframe on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 03 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/iframe/index.xml" rel="self" type="application/rss+xml"/><item><title>Styling Cusdis: Taking Control of the Iframe Without Touching the Source</title><link>https://klikukliku.dev/posts/cusdis-custom-styles/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/cusdis-custom-styles/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;I recently looked into implementing a comment system based on Cusdis. It&amp;rsquo;s a lightweight and privacy-friendly solution, but it comes with a UI challenge: the widget renders inside an &lt;code&gt;iframe&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;What does this mean for us? An iframe creates an isolated environment. The CSS styles we have in our project don&amp;rsquo;t leak inside. As a result, if our layout has specific branding, the default, minimalist Cusdis design looks like a part of something else.&lt;/p&gt;</description></item></channel></rss>