{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/444edb44d9344f5eab46b20200cbf56c\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/444edb44d9344f5eab46b20200cbf56c-0dce9d1040baed56.gif","duration":70.14,"title":"Resolving the Double Range Issue in TabsPanel","description":"In this video, I explain the reason behind the double range issue we encountered in the TabsPanel. It turns out that the TabsPanel was initialized twice due to the attribute change and setting the new active tab, which created a race condition. I suggest that we initialize the range along with the options when creating a new attribute to prevent this from happening again. Please take a moment to review this and let me know your thoughts."}