<%!-- This is an auth page, so it renders through AuthPageWrapper like the other ten. It used to call LayoutWrapper.app_layout directly, which made it the one page that would have kept the host's chrome after auth stopped rendering inside it — the exact "miss one and it silently behaves differently" hazard that using the component rather than a route list is meant to remove. --%> <%!-- Every row of the device panel is behind a presence guard, so a request we know nothing identifying about renders as an empty box — which reads as "still loading" on the one screen where the details ARE the decision. Say which it is, rather than leaving a blank panel to be read as either. --%>

{gettext("No device details could be determined for this request.")}