{"version":"2.1.248","anchor":"panel-versus-dialog-precedence-rule-wired-through-the-reques","canonical_anchor":"panel-versus-dialog-precedence-rule-wired-through-the-reques","heading":"Panel-versus-dialog precedence rule wired through the request path","tier":"notice","area":"UI Panels","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/panel-versus-dialog-precedence-rule-wired-through-the-reques","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Panel-versus-dialog precedence rule wired through the request path\n\nAbout 25 request types now declare they yield to an open panel.\n\n**What**\n\nControl requests now carry a yields-to-panels flag alongside whether the user invoked them, and roughly 25 descriptors hardcode it on, including goal proposals, embedded UI, the managed-settings security notice and sandbox network approval. Two consumers read it, and the active-dialog selector uses it to suppress a dialog while a panel is open. Nothing gates it; each descriptor sets the value as a constant.\n\n**Details**\n\n- The flag travels with the request rather than being decided by the dialog code.\n- Absent entirely in v2.1.247, so the whole precedence rule is new this release.\n\n**Evidence**\n\n`yieldsToPanels`\n\n- Area: UI Panels\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}