/* Stone-first search styles for INTERNAL pages (base.html shell).
 *
 * Same rules as combobox.css and for the same reason: base.html loads the
 * COMPILED tailwind.css, and these rows are built in JS at runtime, so they are
 * authored against the internal token hexes by hand instead of relying on a
 * Tailwind rebuild. Deliberately matched to .sda-cbx so the two pickers on the
 * same form read as one control family: same panel, same active tint, same
 * radii. Quiet: no gradients, no pill radii, no hover scale.
 */

.sda-ss { position: relative; }

.sda-ss ul.sda-ss__list {
  position: absolute;
  z-index: 60;
  left: 0;
  right: 0;
  margin-top: 4px;
  max-height: 18rem;
  overflow-y: auto;
  background: #fff8f4;
  border: 1px solid #dac1b9;
  border-radius: 0.5rem;
  padding: 4px;
  box-shadow: 0px 4px 20px rgba(61, 52, 42, 0.12);
  list-style: none;
}
.sda-ss ul.sda-ss__list[hidden] { display: none; }

.sda-ss .sda-ss__opt {
  padding: 0.45rem 0.6rem;
  border-radius: 0.375rem;
  cursor: pointer;
}
.sda-ss .sda-ss__opt.is-active,
.sda-ss .sda-ss__opt:hover { background: #fbebdc; }

/* Stone name, then the family (and the alias or locality that matched). The
 * second line is the whole point of the control: it teaches where the stone was
 * filed, so the next search can go straight to the select if the maker prefers.
 */
.sda-ss .sda-ss__name {
  display: block;
  font-size: 15px;
  line-height: 22px;
  color: #221a11;
}
.sda-ss .sda-ss__meta {
  display: block;
  font-size: 12px;
  line-height: 18px;
  letter-spacing: 0.02em;
  color: #54433d;
}

.sda-ss .sda-ss__empty {
  padding: 0.45rem 0.6rem;
  font-size: 14px;
  line-height: 20px;
  color: #54433d;
  cursor: default;
}