next to the // Disable panel, and a form cannot wrap two elements with // the Delete panel sitting between them. Harmless for a // tablist: only the active panel is rendered, and the // aria-controls / aria-labelledby pair carries the // relationship rather than source order. ?>
spanning both settings tabs, deliberately. // A settings-screen save runs apply_settings() with // $preserve_existing = false, which clears every option // the payload omits — so two forms would mean saving // one tab wiped the other tab's settings. A panel // hidden by the tab CSS still serializes; only // `disabled` fields are left out. ?>