@charset "UTF-8";
/**
* :::important
* The `limel-radio-button` component can be used inside the HTML of
* other components to render a decorative radio button in
* their UI. An example of this is the list component.
* This means the content of `limel-radio-button` will become a part of the
* consumer's DOM structure.
*
* Additionally, the consumer components also need to import the current `.scss`
* file into their own styles file for the radio button to be rendered correctly!
* This means, if the styles in this file are not "specific" enough,
* there is a risk that the consumer component's styles are affected by
* our styles here.
*
* For instance if the consumer has a `<label>`,
* it might unintentionally inherit styles from the radio button; unless we
* make the such styles more specific here.
*
* Naturally, we cannot mitigate all sorts of potential styling problems.
* The consumer component should be aware of this issue too.
* But we can ensure that our styles here both make sense,
* are readable, and are as specific as possible to avoid unintended side effects.
* :::
*/
/**
* Note! This file is forwarded via `src/style/exports.scss`
* and exposed to consumers through the root `index.scss`.
*
* Consumers import it using:
* `@use '@limetech/lime-elements' as lime-elements;`
*
* Legacy import paths (`dist/scss/mixins`) are maintained
* for backward compatibility via copy rules in the Stencil config.
*/
/**
* This can be used on a trigger element that opens a dropdown menu or a popover.
*/
/**
 * This mixin will mask out the content that is close to
 * the edges of a scrollable area.
 * - If the scrollable content has `overflow-y`, use `vertically`
 * as an argument for `$direction`.
 - If the scrollable content has `overflow-x`, use `horizontally`
 * as an argument for `$direction`.
 *
 * For the visual effect to work smoothly, we need to make sure that
 * the size of the fade-out edge effect is the same as the
 * internal paddings of the scrollable area. Otherwise, content of a
 * scrollable area that does not have a padding will fade out before
 * any scrolling has been done.
 * This is why this mixin already adds paddings, which automatically
 * default to the size of the fade-out effect.
 * This size defaults to `1rem`, but to override the size use
 * `--limel-top-edge-fade-height` & `--limel-bottom-edge-fade-height`
 * when `vertically` argument is set, and use
 * `--limel-left-edge-fade-width` & `--limel-right-edge-fade-width`
 * when `horizontally` argument is set.
 * Of course you can also programmatically increase and decrease the
 * size of these variables for each edge, based on the amount of
 * scrolling that has been done by the user. In this case, make sure
 * to add a custom padding where the mixin is used, to override
 * the paddings that are automatically added by the mixin in the
 * compiled CSS code.
 */
/**
* This mixin will add an animated underline to the bottom of an `a` elements.
* Note that you may need to add `all: unset;` –depending on your use case–
* before using this mixin.
*/
/**
* This mixin creates a cross-browser font stack.
* - `sans-serif` can be used for the UI of the components.
* - `monospace` can be used for code.
*
* ⚠️ If we change the font stacks, we need to update
* 1. the consumer documentation in `README.md`, and
* 2. the CSS variables of `--kompendium-example-font-family`
* in the `<style>` tag of `index.html`.
*/
/**
* This mixin is a hack, using old CSS syntax
* to enable you to truncate a piece of text,
* after a certain number of lines.
*/
/**
* This mixin will add a chessboard background pattern,
* typically used to visualize transparency.
*/
/**
* Make a container resizable by the user.
* This is used in the documentations and examples
* of some components, to demonstrate how the component
* behaves in a resizable container.
*/
/**
 * Drag to reorder mixins
 */
/**
 * The breakpoints below are used to create responsive designs
 * in Lime's products. Therefore, they are here to get distributed
 * to all components in other private repos, which rely on this `mixins`
 * file, to create consistent styles.
 *
 * :::important
 * In very rare cases you should used media queries!
 * Nowadays, there are many better ways of achieving responsive design
 * without media queries. For example, using CSS Grid, Flexbox, and their features.
 * :::
 */
/**
  * Media query mixins for responsive design based on screen width.
  * Note that these mixins do not detect the device type!
  */
/**
* :::important
* The `limel-radio-button` component can be used inside the HTML of
* other components to render a decorative radio button in
* their UI. An example of this is the list component.
* This means the content of `limel-radio-button` will become a part of the
* consumer's DOM structure.
*
* Additionally, the consumer components also need to import the current `.scss`
* file into their own styles file for the radio button to be rendered correctly!
* This means, if the styles in this file are not "specific" enough,
* there is a risk that the consumer component's styles are affected by
* our styles here.
*
* For instance if the consumer has a `<label>`,
* it might unintentionally inherit styles from the radio button; unless we
* make the such styles more specific here.
*
* Naturally, we cannot mitigate all sorts of potential styling problems.
* The consumer component should be aware of this issue too.
* But we can ensure that our styles here both make sense,
* are readable, and are as specific as possible to avoid unintended side effects.
* :::
*/
*,
*:before,
*:after {
  box-sizing: border-box;
}

.boolean-input {
  --limel-boolean-input-box-size: 1.25rem;
  --limel-boolean-input-gap-size: 0.5rem;
  position: relative;
  isolation: isolate;
  display: flex;
  align-items: center;
  min-height: var(--limel-checkbox-min-height, 2.5rem);
  width: 100%;
}
.boolean-input input[type=checkbox],
.boolean-input input[type=radio] {
  position: absolute;
  width: 0;
  height: 0;
  margin: -1px;
  padding: 0;
  border: 0;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  clip-path: inset(50%);
  white-space: nowrap;
  -webkit-appearance: none;
  -moz-appearance: none;
  appearance: none;
}

label.boolean-input-label {
  min-width: var(--limel-boolean-input-box-size);
  min-height: var(--limel-boolean-input-box-size);
  padding-top: 0.125rem;
  cursor: pointer;
  position: relative;
  width: 100%;
  overflow-wrap: var(--limel-boolean-input-label-overflow-wrap, normal);
  font-size: var(--limel-theme-default-small-font-size);
  color: var(--limel-theme-text-primary-on-background-color);
  padding-left: calc(var(--limel-boolean-input-box-size) + var(--limel-boolean-input-gap-size));
}
.disabled:not([readonly]):not([readonly=true]) label.boolean-input-label {
  cursor: not-allowed;
  color: var(--limel-theme-text-disabled-color);
}
.required label.boolean-input-label:after {
  margin-left: 0.0625rem;
  content: "*";
}
.invalid:not(.readonly) label.boolean-input-label {
  color: var(--limel-theme-error-text-color);
}
:host(limel-checkbox.hide-label) label.boolean-input-label, .hide-label label.boolean-input-label {
  overflow: hidden;
  white-space: nowrap;
  text-overflow: ellipsis;
  opacity: 0;
  width: var(--limel-boolean-input-box-size);
}

.box {
  position: absolute;
  pointer-events: none;
  transition: border-color 0.4s ease 0.2s, background-color 0.2s ease, box-shadow var(--limel-clickable-transform-speed, 0.4s) ease;
  display: inline-block;
  vertical-align: middle;
  width: var(--limel-boolean-input-box-size);
  height: var(--limel-boolean-input-box-size);
  margin-right: var(--limel-boolean-input-gap-size);
  border-radius: var(--limel-boolean-input-box-border-radius);
  border: 0.125rem solid;
  border-color: var(--checkbox-unchecked-border-color, rgb(var(--contrast-900)));
  background-color: var(--limel-checkbox-background-color, rgb(var(--contrast-300)));
  /*
   * NOTE: Original selectors using `:has()` are commented out due to Safari
   * rendering bugs where descendant transitions (e.g. SVG stroke animations)
   * or box/background updates sometimes fail to animate or even repaint
   * reliably when the state change is detected only via `:has()`.
   *
   * Original (kept for future re-implementation, or cleanup):
   * .boolean-input:has(input[type='checkbox']:checked) &,
   * .boolean-input:has(input[type='radio']:checked) & {
   *   ...
   * }
   *
   * Replacement uses adjacency: the markup places the `<input>` immediately
   * before .box, so we can select the checked state with
   * input:checked + .box. We retain the explicit `.checked` class pathway in
   * case some templates toggle that class manually.
   *
   * Using the `:has()` selector is more reliable, because it doesn't
   * depend on the DOM structure (e.g. if the markup changes and the input is
   * no longer adjacent to the box), but Safari support for `:has()` is still
   * somewhat inconsistent.
   */
}
.checked .box, .boolean-input > input[type=checkbox]:checked + .box, .boolean-input > input[type=radio]:checked + .box {
  background-color: var(--lime-primary-color, var(--limel-theme-primary-color));
  border-color: var(--lime-primary-color, var(--limel-theme-primary-color));
}
.disabled .box {
  opacity: 0.4;
}
.box {
  /*
   * See previous comment about Safari rendering bugs ☝️.
   *
   * Original (kept for for future re-implementation, or cleanup):
   * .boolean-input:not(.disabled):has(label.boolean-input-label:hover) & { ... }
   * .boolean-input:not(.disabled):has(label.boolean-input-label:active) & { ... }
   */
}
.boolean-input:not(.disabled):hover .box {
  will-change: box-shadow;
  box-shadow: var(--button-shadow-hovered);
}
.boolean-input:not(.disabled):active .box {
  will-change: box-shadow;
  box-shadow: var(--button-shadow-pressed);
}
.box:before {
  transition: color var(--limel-clickable-transition-speed, 0.4s) ease, background-color var(--limel-clickable-transition-speed, 0.4s) ease, box-shadow var(--limel-clickable-transform-speed, 0.4s) ease, transform var(--limel-clickable-transform-speed, 0.4s) var(--limel-clickable-transform-timing-function, ease);
  content: "";
  position: absolute;
  inset: -0.1875rem;
  border-radius: inherit;
  /*
   * See previous comment about Safari rendering bugs ☝️.
   *
   * Original (kept for for future re-implementation, or cleanup):
   * .boolean-input:has(input[type='checkbox']:focus-visible) &,
   * .boolean-input:has(input[type='radio']:focus-visible) & { ...}
   */
}
.boolean-input > input[type=checkbox]:focus-visible + .box:before, .boolean-input > input[type=radio]:focus-visible + .box:before {
  will-change: box-shadow;
  box-shadow: var(--shadow-depth-8-focused);
}
.box:after {
  transition: opacity 0.2s ease, width 0.4s ease, box-shadow 0.6s cubic-bezier(0.68, -0.55, 0, 1.87), transform 0.6s cubic-bezier(0.68, -0.55, 0, 1.87);
  content: "";
  position: absolute;
  inset: 0;
  margin: auto;
  border-radius: 1rem;
  opacity: 0;
  background-color: rgb(var(--color-white));
  /* Hover fallback for pseudo-element (see explanation above). */
}
.boolean-input:not(.disabled):hover .box:after {
  will-change: opacity, box-shadow, transform, width;
}

.radio-button {
  --limel-boolean-input-box-border-radius: var(
      --limel-boolean-input-box-size
  );
}
.radio-button .box:after {
  width: 100%;
  height: 100%;
  border-radius: 50%;
}

.boolean-input:has(input[type=radio]:checked) .box:after {
  opacity: 1;
  transform: scale(0.6);
  box-shadow: var(--shadow-depth-8);
}