/* Proceedings - site styles; YOOtheme/UIkit classes do the heavy lifting. */
.proceedings-search .uk-grid > * { margin-bottom: 10px; }
.proceedings-item + .proceedings-item { border-top: 1px solid #e5e5e5; padding-top: 20px; margin-top: 20px; }
.proceedings-item .proceedings-authors { color: #666; }
.proceedings-meta dt { font-weight: 600; }

/* On a phone the search form shows its essentials only: the query field and the two buttons.
   Every other cell carries proceedings-filter and folds away behind the toggle, which is itself
   hidden from @s up (640px), so from there the filters are simply always there and these rules
   never apply. The column classes go on beyond that: two filters per row from @s, and the
   desktop layout only from @m (960px), because at 641px a quarter-width select is about 140px
   and a committee reads "TC10 - Measurement for Diagnostics, Optimization and Control".

   Everything below is keyed on proceedings-js, which the form only adds once it has seen UIkit
   running. Hiding is the dangerous half here, because only UIkit's Toggle can undo it, so
   nothing is hidden until the thing that can bring it back is known to be there. A site without
   UIkit, a script that failed to load or errored, JavaScript switched off: in all of them the
   filters stay visible and the button that could not have worked stays out of the way. */
@media (max-width: 639px) {
    .proceedings-search .proceedings-filters-toggle { display: none; }
    .proceedings-search.proceedings-js .proceedings-filters-toggle { display: block; }
    .proceedings-search.proceedings-js .proceedings-filter { display: none; }
    .proceedings-search.proceedings-js.proceedings-filters-open .proceedings-filter { display: block; }
}