<?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/90f39d46cf4b49cf94c47ebb98645ba3&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/90f39d46cf4b49cf94c47ebb98645ba3-3db605ed0f28019e.gif</thumbnail_url><duration>89.067</duration><title>Discourse context update bug with sidebar</title><description>This Loom discusses a bug where discourse context relationships fail to update when a page is opened on the sidebar before navigating to the main page. The author explains that opening a claim from the sidebar, then adding it under the opposes section, does not create the expected relation in the discourse node. However, when the claim is not opened via the sidebar and is instead created directly, the relation is successfully created in the discourse context panel. The key point is that the issue depends on whether the page was initially opened in the sidebar.</description></oembed>