PrimeNG v18 Nested Dialog focus restoration still unreliable

Goal

Ensure that closing a child Dialog returns focus to the element that opened the parent Dialog, satisfying WCAG 2.4.3.

Likely Explanation

PrimeNG’s focus‑trap service stores a single reference to the element that had focus when a dialog is opened. In a nested scenario the child dialog’s trigger overwrites that reference, so when the child is closed the stored reference points to the child’s trigger (or the parent dialog itself) instead of the original parent trigger.

Confirmed Facts

• The focusTrap option (global or per‑dialog) is respected for each dialog instance but does not prevent the overwrite of the stored focus reference.
• Disabling the global focusTrap via providePrimeNG({ accessibility: { focusTrap: false } }) does not change this behavior.
• The (onHide) event fires after the dialog is hidden, providing a chance to restore focus manually.

Recommended Steps (minimal)

1. Capture the element that opens the parent dialog (e.g., via @ViewChild or a signal‑based viewChild).
2. Store that reference in a component property or signal.
3. On the child dialog, listen to its (onHide) event and, when triggered, call focus() on the stored reference if it is focusable.
4. Enable focusTrap on both dialogs (globally or via [focusTrap]="true").

Missing Diagnostic Detail

Are you using signal‑based components (with signal() and viewChild()) or classic Angular class components? This determines whether you store the trigger in a signal or a class property, but the overall pattern remains the same.