@charset "UTF-8";
/**
* Root-level entry point for consuming @limetech/lime-elements SCSS utilities.
*
* This file enables the clean import path:
* `@use '@limetech/lime-elements' as lime-elements;`
*
* It simply forwards everything from the built exports file.
*/
/**
* Public SCSS exports for consumers of @limetech/lime-elements.
*
* This file provides reusable styling utilities.
*
* Import this file using:
* `@use '@limetech/lime-elements' as lime-elements;`
*
* For detailed documentation of each utility, its parameters,
* and usage examples, refer to the respective source files.
*/
/**
* 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.
*/
/**
* Neutralizes the user-agent styles that browsers apply to `<button>` elements
* (their default background, border, padding, font, etc.), without stripping
* the useful defaults that `all: unset;` would also remove
* (such as `display`, `cursor`, and focus behavior).
*
* Prefer this mixin over `all: unset;` on `<button>` elements, then layer
* the styling you want on top — often one of the `is-*-clickable` mixins.
*/
/**
* 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!
  */
/**
* @mixin action-bar-interactions($item-selector)
* This mixin applies styles for the action bar interactions.
* For example, it animates the height of the action bar from `0` to `auto`.
*
* :::note
* The consumer should set:
* `--limebb-promoted-action-bar-grid-template-rows: 0fr;`
* when the action bar is not supposed to be visible.
* :::
*
* @param {string} $item-selector - The consumer component's tag name for the item that displays the action bar.
*/
.expression {
  display: flex;
  flex-direction: column;
  margin-bottom: 1rem;
  gap: 1rem;
  padding: 1rem;
  border-left: 0.25rem solid rgb(var(--contrast-400));
  background-color: rgb(var(--contrast-100));
}