<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/fd48ef9fbd014138bec738530186d2cb&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/fd48ef9fbd014138bec738530186d2cb-00001.gif</thumbnail_url><duration>769.5799999999999</duration><title>Exploring the Limitations of Webflow&apos;s Editor [🎥]</title><description>In this video, I delve into the intricacies of Webflow&apos;s editor and discuss the challenges I encountered while trying to modify empty fields. I highlight the progression of changes that occur when the page loads and the editor mode takes effect. I also demonstrate the use of a mutation observer to detect when the editor has loaded and the fields are ready for modification. However, I uncover a flaw in the system where typing content programmatically does not register as actual content. Despite the issues faced, this exploration provides valuable insights into the editor&apos;s limitations and design artifacts.</description></oembed>