<?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/aad654710f5a413fa819dadf9252dfbd&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/aad654710f5a413fa819dadf9252dfbd-444b570ccbf6674e.gif</thumbnail_url><duration>73.814</duration><title>Context Menu Event Handling Explained 🖱️</title><description>In this video, I discuss the implementation of a forced context menu event triggered by a right-click action, which was necessary due to issues with the CDN handling the right-click event. This approach ensures that the canvas properly renders the context menu, regardless of whether the click is on a shape or empty space. I believe this method is effective, but I acknowledge that there could be scenarios where the right-click might need to perform differently. I encourage everyone to consider these points and be prepared to discuss them in our upcoming all-hands meeting.</description></oembed>