/*
 * This is a manifest file that'll be compiled into application.css.
 *
 * With Propshaft, assets are served efficiently without preprocessing steps. You can still include
 * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard
 * cascading order, meaning styles declared later in the document or manifest will override earlier ones,
 * depending on specificity.
 *
 * Consider organizing styles into separate files for maintainability.
 */

input[type="checkbox"].fancy {
  display: none;
}

input[type="checkbox"] ~ .check-glyph-checked {
  display: none;
}

input[type="checkbox"]:checked ~ .check-glyph-unchecked {
  display: inline;
}

input[type="checkbox"]:checked ~ .check-glyph-unchecked {
  display: none;
}

input[type="checkbox"]:checked ~ .check-glyph-checked {
  display: inline;
}

table.snork {
  thead { display: none; }
}

table.snork:has(tbody tr) {
  thead { display: table-header-group; }
}

table.snork:has(tbody tr) + .blank-slate {
  display: none;
}

ul.snork:has(li) + .blank-slate {
  display: none;
}

div.table.snork:has(.table-data-row) + .blank-slate {
  display: none;
}

.snork:has(table tbody tr) .blank-slate {
  display: none;
}

.snork:has(*) + .blank-slate {
  display: none;
}

ol.snork:has(li) + .blank-slate {
  display: none;
}

ul.snork:has(li) + .blank-slate {
  display: none;
}

summary::marker, /* Latest Chrome, Edge, Firefox */ 
summary::-webkit-details-marker /* Safari */ {
  display: none;
  content: "";
}

.visibility-toggle:has(:checked) {
  display: none;
}

.visibility-toggle ~ .visibility-toggle-target {
  display: none;
}

.visibility-toggle:has(:checked) + .visibility-toggle-target {
  display: block;
}

.dropdown .menu {
  display: none;
}

.dropdown:has(:checked) .menu {
  display: block;
}

.empty-hidden:empty {
  display: none;
}