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

.embedded-sections {
  display: grid;
  gap: 1rem;
}

.embedded-section-tracks {
  container-type: inline-size;
  min-block-size: 3rem;
}

.embedded-track-row {
  display: grid;
  grid-template-columns: auto minmax(0, 1fr) auto;
  align-items: center;
  gap: 0.5rem;
}

.embedded-track-details {
  min-width: 0;
  overflow-wrap: anywhere;
}

.embedded-track-actions {
  grid-column: 3;
  grid-row: 1;
}

.embedded-track-audio {
  grid-column: 2 / -1;
  width: 100%;
  min-width: 0;
  height: 2rem;
}

@container (min-width: 560px) {
  .embedded-track-row {
    grid-template-columns: auto minmax(0, 1fr) minmax(180px, 240px) auto;
  }

  .embedded-track-audio {
    grid-column: 3;
    grid-row: 1;
  }

  .embedded-track-actions {
    grid-column: 4;
  }
}

.embedded-upload-preview {
  display: block;
  width: 100%;
  max-height: 12rem;
  object-fit: contain;
  pointer-events: none;
}

.embedded-upload-preview[hidden] {
  display: none;
}

.embedded-product-details {
  min-width: 0;
  overflow-wrap: anywhere;
}

.embedded-visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}
