{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/ca385f8fb07d4873aa0b7879ac73e1e6\" frameborder=\"0\" width=\"1426\" height=\"1069\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1069,"width":1426,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1069,"thumbnail_width":1426,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/ca385f8fb07d4873aa0b7879ac73e1e6-c81c04805ae561ab.gif","duration":145.1382,"title":"Issue with disabled state being passed through on steps component","description":"In this video, I discuss a bug I've encountered with the steps component, specifically regarding the disabled properties not functioning as expected. I've demonstrated this with a basic example and compared it to an Ant D version where the disabled states are correctly applied. It's clear that the current implementation isn'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."}