/*
 * 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.
 */


.ts-wrapper .clear-button {
  font-size: 1.25rem;
  padding-bottom: 0.7rem;
  cursor: pointer;
  color: #555;
}

.ts-wrapper .clear-button:hover {
  color: #000;
}

/* Pagination Styles */
.pagy-nav {
  display: flex;
  justify-content: center;
  align-items: center;
  gap: 0.5rem;
  margin: 1.5rem 0;
}

.pagy-nav .page {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 2.5rem;
  height: 2.5rem;
  padding: 0 0.75rem;
  border: 1px solid #d1d5db;
  border-radius: 0.375rem;
  background-color: white;
  color: #374151;
  text-decoration: none;
  font-size: 0.875rem;
  font-weight: 500;
  transition: all 0.15s ease-in-out;
}

.pagy-nav .page:hover {
  background-color: #f9fafb;
  border-color: #9ca3af;
  color: #111827;
}

.pagy-nav .page.active {
  background-color: #3b82f6;
  border-color: #3b82f6;
  color: white;
}

.pagy-nav .page.disabled {
  background-color: #f3f4f6;
  border-color: #e5e7eb;
  color: #9ca3af;
  cursor: not-allowed;
}

.pagy-nav .page.prev,
.pagy-nav .page.next {
  font-weight: 600;
}

.pagy-nav .page.prev:before {
  content: "←";
  margin-right: 0.25rem;
}

.pagy-nav .page.next:after {
  content: "→";
  margin-left: 0.25rem;
}