<?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/17f8c56f0d8d41a58fc71df6960e2732&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/17f8c56f0d8d41a58fc71df6960e2732-6bf43dcd3326f4c6.gif</thumbnail_url><duration>47.126</duration><title>Testing Back Navigation in Event Workflow</title><description>This Loom tests an event-based workflow back navigation behavior and checks whether parameters still work. After applying a diff and navigating into the event-based workflow, the author clicks back once and confirms the flow returns correctly. They then verify that keyboard shortcuts still open the chat using Control-A or Command-K. Pressing back again removes the browser bar chat history, which they note is not ideal but acceptable.</description></oembed>