/* Desktop shell only. Every rule here is behind a class the shell puts on the
   root element, so a plain browser loads this file and nothing in it applies. */

/* The operating system draws a real title bar, so ours would be a second one
   stacked on top of it. The menu bar stays: that is part of the app, not part
   of the window frame. */
.is-native .titlebar { display: none; }
.is-native body { padding: 0; }
.is-native .window-app { max-width: none; border: none; border-radius: 0; box-shadow: none; }

/* ---------- the contact list window ---------- */

.mode-contacts .pane-chat { display: none; }
.mode-contacts .pane-contacts { width: 100%; border-right: none; }
/* Its own window, so there is nothing to sign out of in a title bar and no
   conversation to be in. */
.mode-contacts .chat-empty { display: none; }

/* ---------- a conversation window ---------- */

.mode-conv .pane-contacts { display: none; }
.mode-conv .pane-splitter { display: none; }
/* One conversation per window means no tab strip and no way to close the last
   tab into an empty window. The window close button is the way out. */
.mode-conv .tabstrip { display: none; }
.mode-conv .chat-empty { display: none; }
.mode-conv .menubar { display: none; }
.mode-conv .ad-strip { display: none; }

/* The desktop has room for the display pictures at every width, since the
   window is only ever one conversation wide. */
.mode-conv .dp-column { display: flex; }

@media (max-width: 820px) {
  .mode-conv .pane-chat { display: flex; }
  .mode-contacts .pane-contacts { display: flex; }
}