A just in case reminder about !2068 and navbar breaking with apps that don't request comctl v6 without it so this is not accidentally merged.
On a side note, the me breaking keyboard navigation before was due to arrows leaving sticky highlight, looked into it a bit further and turns out it comes from `DEFDLG_SetDefButton` setting `BS_DEFPUSHBUTTON` to the buttons, and causing them to have `STATE_DEFAULTED` draw state.
This can still happen with, for example, tabbing to Desktop crumb, and then opening another folder, can be hacked around by subclassing `WM_GETDLGCODE` and unsetting `DLGC_UNDEFPUSHBUTTON`, but would that break something unintentionally?