/*
 * ICC-039-specific correction for chrome.css -- NOT part of 440-site-chrome,
 * so not copied into 440-indicators. chrome.css's theme.json export
 * (tokens.css) styles wp-element-button through :where(...), so a consuming
 * theme can override it cheaply. But :where() contributes zero specificity,
 * and this app already has its own normalize-style reset scoped under
 * .voila-content (pasted into App.svelte's <style>, see its
 * "a{background-color:transparent;color:inherit}" and
 * "*{margin:0;padding:0;...}" rules) that ties or outranks that :where() rule
 * -- so buttons (e.g. the header's Subscribe) were losing their
 * background/padding to that reset. Re-asserting the same declarations with
 * real (non-:where()) specificity fixes it without touching chrome.css.
 *
 * Scoped to .wp-element-button/.wp-block-button__link specifically (not a
 * bare "a" selector) -- chrome.css's own per-component rules (e.g.
 * .site-header__brand, .language-switcher__link) already override plain
 * links at (0,2,0); a broader fix here would outrank those too and underline
 * things that should stay plain, like the header's tagline.
 */

.voila-content .site-chrome :where(.wp-element-button, .wp-block-button__link) {
  background-color: var(--wp--custom--color--action-primary);
  border-radius: var(--wp--custom--radius--default);
  border-width: 0;
  color: var(--wp--custom--color--text-inverse);
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--x-small);
  font-style: inherit;
  font-weight: 600;
  letter-spacing: inherit;
  line-height: var(--wp--custom--line-height--none);
  padding-top: 0.75rem;
  padding-right: 1.375rem;
  padding-bottom: 0.75rem;
  padding-left: 1.375rem;
  text-decoration: none;
  text-transform: inherit;
}
