<?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/1bb67a6488bb40259b38e146fb625ad2&quot; frameborder=&quot;0&quot; width=&quot;1890&quot; height=&quot;1417&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1417</height><width>1890</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1417</thumbnail_height><thumbnail_width>1890</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1bb67a6488bb40259b38e146fb625ad2-d2e4423ebbc05aa4.gif</thumbnail_url><duration>347.006</duration><title>Testing Nested Component Behavior and Property Binding Issues ⚙️</title><description>In this video, I walk through my test page for nested components, highlighting how the child and parent instances behave with shared properties. I noticed that changes made to the child component don&apos;t reflect in the nested instance on the front end, which always defaults to the first option. I also encountered issues with default values not updating correctly, particularly with global CSS properties. My testing revealed that while most property bindings work fine, there are inconsistencies that need addressing. I encourage you to review this behavior and share any insights or solutions you might have.</description></oembed>