Answer
No documented account-level, user-level, or NRQL settings option exists to enable or enforce focus trapping in the NRQL Query Builder modal. Model knowledge does not confirm a configuration toggle or public API for focus-trap behavior, and there is no confirmed plan to expose a flag or API to control it.
Confirmed facts
- New Relic web UI modals are expected to manage keyboard focus for accessibility, including trapping Tab navigation inside the dialog and returning focus to the trigger on close.
- Specific configuration details for the NRQL Query Builder modal are not confirmed in model knowledge.
- New Relic does not expose a documented setting or API to enforce focus-trap behavior for this modal.
Likely explanation
The Query Builder modal is typically a React-based dialog that uses a focus-trap pattern to cycle Tab and Shift+Tab within its interactive elements and prevent focus from moving to background page content while open. Focus escape commonly occurs when content is rendered in a portal outside the trap boundary, when dynamic elements are injected after trap initialization, or when the modal is conditionally rendered causing the trap to be disabled.
Steps needed for this case
- Open the NRQL Query Builder modal in the standard New Relic One UI and confirm it receives initial focus on a logical first control.
- Press Tab repeatedly and Shift+Tab to verify focus cycles only within modal controls and does not reach background page elements.
- Close the modal with Escape or the close button and verify focus returns to the element that opened the Query Builder.
- Inspect the modal container for role="dialog" and aria-modal attributes and confirm focusable elements are descendants of the modal boundary during open state.
If the tests above fail, treat it as an accessibility defect in the product UI and raise it with New Relic support with reproduction steps, browser, and assistive technology used. Do not modify New Relic core UI code; focus management is version-sensitive and changes can be overwritten by product updates.
One missing diagnostic detail that changes the recommendation: clarify whether the issue is in the standard New Relic One web UI Query Builder or in a custom embedded/integrated instance. Configuration options and workarounds differ for custom integrations that re-render modal content.