{"version":3,"file":"blocks/IconList/style-index.css","mappings":";;;AAAA,gBAAgB;AAehB;EACC;EACA;EACA;EAKA;EAEA;EACA;EACA;AAlBD;AAoBC;EACC;EACA;EACA;EACA;AAlBF;AAqBC;EACC;AAnBF;AAsBC;EACC;EACA;EACA;AApBF;AARA;EA+BC;;;;;;;;;IAAA;AAXD;AAsBE;EACC;AApBH;AAuBE;EACC;AArBH;AA0BE;EACC;AAxBH;AA2BE;EACC;AAzBH;AA+BC;EACC;AA7BF;AAgCC;EACC;AA9BF;;AAkCA;EACC;EACA;EACA;AA/BD;AAiCC;EACC;EACA;EACA;AA/BF;AAoCC;EACC;EACA;EACA;EACA;EACA;AAlCF;AAqCC;EACC;AAnCF;;AAuCA;EACC;AApCD,C","sources":["webpack://brandy-blocks/./src/blocks/IconList/style.scss"],"sourcesContent":["// Icon List — shared editor + frontend styles.\n//\n// The parent holds every custom property and the items read them through the\n// cascade. Block context delivers the same numbers to the item's *editor*, but\n// a published page has no context, so the cascade is the single source of\n// truth for both runtimes.\n//\n// SPECIFICITY, AND WHY THE LIST RULES LOOK OVER-QUALIFIED\n// -------------------------------------------------------\n// Brandy's own stylesheet resets lists with a `:not(...)` selector that lands\n// at (0,1,2), which beats a plain `.brandy-icon-list` (0,1,0) and would strip\n// the padding and markers back out. Same trap Table of Contents documents. The\n// rules that a reset can touch are anchored on two classes so they win on any\n// theme.\n\n.brandy-icon-list {\n\t--brandy-icon-list-icon-size: 20px;\n\t--brandy-icon-list-icon-gap: 10px;\n\t--brandy-icon-list-gap: 10px;\n\t// The glyphs are the accent, so they take the site's primary colour while\n\t// the text keeps the theme's. `brandy-primary` is injected per niche by\n\t// AbstractNicheSetup::update_theme_json(); on a non-Brandy theme the\n\t// fallback restores the old inherit-the-text behaviour.\n\t--brandy-icon-list-icon-color: var(--wp--preset--color--brandy-primary, currentColor);\n\n\tbox-sizing: border-box;\n\tdisplay: flex;\n\tgap: var(--brandy-icon-list-gap);\n\n\t&.brandy-icon-list {\n\t\tmargin-left: 0;\n\t\tmargin-right: 0;\n\t\tpadding: 0;\n\t\tlist-style: none;\n\t}\n\n\t&.is-layout-vertical {\n\t\tflex-direction: column;\n\t}\n\n\t&.is-layout-horizontal {\n\t\tflex-direction: row;\n\t\tflex-wrap: wrap;\n\t\talign-items: center;\n\t}\n\n\t/*\n\t * Alignment, expressed against whichever axis the list is running on.\n\t *\n\t * One control, two meanings: in a vertical list the lines stack, so moving\n\t * them across the list is `align-items`; laid out in a row it is\n\t * `justify-content`. Asking the author which CSS property they meant would\n\t * be asking them to know the layout switch's implementation.\n\t *\n\t * `left` is the default and says nothing — see getWrapperClasses().\n\t */\n\t&.is-layout-vertical {\n\t\t&.is-align-center {\n\t\t\talign-items: center;\n\t\t}\n\n\t\t&.is-align-right {\n\t\t\talign-items: flex-end;\n\t\t}\n\t}\n\n\t&.is-layout-horizontal {\n\t\t&.is-align-center {\n\t\t\tjustify-content: center;\n\t\t}\n\n\t\t&.is-align-right {\n\t\t\tjustify-content: flex-end;\n\t\t}\n\t}\n\n\t// A centred or right-aligned line reads as centred/right-aligned text too;\n\t// leaving the text hard left inside a centred row looks like a mistake.\n\t&.is-align-center .brandy-icon-list__text {\n\t\ttext-align: center;\n\t}\n\n\t&.is-align-right .brandy-icon-list__text {\n\t\ttext-align: end;\n\t}\n}\n\n.brandy-icon-list__item {\n\tdisplay: flex;\n\talign-items: center;\n\tgap: var(--brandy-icon-list-icon-gap);\n\n\t&.brandy-icon-list__item {\n\t\tmargin: 0;\n\t\tpadding: 0;\n\t\tlist-style: none;\n\t}\n\n\t// The glyph sits on the first line of text rather than centred against the\n\t// whole item: a three-line entry with a centred icon reads as unattached.\n\ti {\n\t\tflex: 0 0 auto;\n\t\tdisplay: block;\n\t\tfont-size: var(--brandy-icon-list-icon-size);\n\t\tline-height: inherit;\n\t\tcolor: var(--brandy-icon-list-icon-color);\n\t}\n\n\ta {\n\t\tcolor: inherit;\n\t}\n}\n\n.brandy-icon-list__text {\n\tmin-width: 0;\n}\n"],"names":[],"sourceRoot":""}