{"version":"2.1.271","anchor":"plugin-render-hover-now-dispatches-cross-plugin-scope-tracki","canonical_anchor":"plugin-render-hover-now-dispatches-cross-plugin-scope-tracki","heading":"Plugin render hover now dispatches cross-plugin scope tracking","tier":"internal","area":"Plugin UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-render-hover-now-dispatches-cross-plugin-scope-tracki","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin render hover now dispatches cross-plugin scope tracking\n\nPlugin rendering now tracks hover across plugin boundaries, not just draw ownership\n\n**What**\n\nWhen a plugin's render hook returns a UI component that was actually drawn by another plugin, and that component has a `hover` property, the rendering engine now records a hover-scope binding tying the hover state to that other plugin. Previously this situation was only checked to validate which plugin was allowed to draw the component, without tracking hover across the boundary.\n\n**Why**\n\nThis lets hover state work correctly when one plugin reuses or wraps a component drawn by another plugin, rather than only enforcing draw ownership.\n\n- Area: Plugin UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}