<?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/ca385f8fb07d4873aa0b7879ac73e1e6&quot; frameborder=&quot;0&quot; width=&quot;1426&quot; height=&quot;1069&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1069</height><width>1426</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1069</thumbnail_height><thumbnail_width>1426</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ca385f8fb07d4873aa0b7879ac73e1e6-c81c04805ae561ab.gif</thumbnail_url><duration>145.1382</duration><title>Issue with disabled state being passed through on steps component</title><description>In this video, I discuss a bug I&apos;ve encountered with the steps component, specifically regarding the disabled properties not functioning as expected. I&apos;ve demonstrated this with a basic example and compared it to an Ant D version where the disabled states are correctly applied. It&apos;s clear that the current implementation isn&apos;t honoring the disabled property, which is causing confusion for users. I would appreciate your thoughts on this issue and any suggestions for a fix.</description></oembed>