/* * Presentation mode (`?mode=presentation`, see lib/js/utils/presentation.js). * * Everything here hangs off `data-zaya-mode="presentation"` on , which is set by a script * in the before the body is parsed, so an embedded reader never paints its chrome first. * This sheet is linked last, after shell.css, so it wins by order rather than by !important. * * What goes: the header, both drawers and their scrim, the dialogs, and every bar control that * opens one of them (Navigator, search, share, the More menu). What stays: the page controls, * zoom, fullscreen, and a sound button that exists only here, because the More menu that * normally carries it is gone. * * Hiding a control is not what stops it: the features ask `window.ZayaPresentation.active` * before opening a drawer or acting on a shortcut, so a keystroke cannot reach what the bar no * longer offers. This sheet only says what is seen. */ /* A control the bar shows only in presentation mode. */ .presentation-only { display: none; } [data-zaya-mode="presentation"] .presentation-only { display: flex; } /* The chrome. The header and the drawers are fixed overlays, so removing them moves nothing. */ [data-zaya-mode="presentation"] #appHeader, [data-zaya-mode="presentation"] #navigatorDrawer, [data-zaya-mode="presentation"] #unifiedPanel, [data-zaya-mode="presentation"] #drawerScrim, [data-zaya-mode="presentation"] #printDialog, [data-zaya-mode="presentation"] #pdfSpecificQuotesModal { display: none; } /* The bar controls that belong to the chrome, and the separator that grouped them. */ [data-zaya-mode="presentation"] #customThumbnailBtn, [data-zaya-mode="presentation"] #customOutlineBtn, [data-zaya-mode="presentation"] #customSearchBtn, [data-zaya-mode="presentation"] #customShareBtn, [data-zaya-mode="presentation"] .more-menu-anchor, [data-zaya-mode="presentation"] [data-bar-sep="navigator"] { display: none; }