{"version":3,"file":"blocks/PinnedNotes/style-index.css","mappings":";;;AAMA;EAQE;AAZF;;AA4BE;EACE;AAzBJ;;AAwBE;EACE;AArBJ;;AAoBE;EACE;AAjBJ;;AAgBE;EACE;AAbJ;;AAYE;EACE;AATJ;;AAQE;EACE;AALJ;;AAIE;EACE;AADJ;;AAAE;EACE;AAGJ;;AACA;EACE;AAEF;;AASA;EACE;IACE;EANF;AACF;AAwBA;EACE;IACE;EAtBF;AACF;AAyBA;EACE;IACE;EAvBF;AACF,C","sources":["webpack://brandy-blocks/./src/blocks/PinnedNotes/style.scss"],"sourcesContent":["// Pinned Notes — the arrangement layer for a row of pinned note cards.\n//\n// Columns, gap and alignment are core's grid layout support. This file adds\n// only what core has no concept of: the stagger, and the gutter that catches\n// tilted corners.\n\n.brandy-pinned-notes {\n  // A rotated card overflows its own layout box — the corners swing outside it,\n  // roughly 7px at 2° on a 470px card. Between columns the grid gap absorbs\n  // that; at the first and last column it lands here. This is the only element\n  // that can catch it, which is exactly why the notes needed a parent.\n  //\n  // Author padding from the spacing support serializes inline and wins, so this\n  // is a floor rather than a fixed value.\n  padding-inline: 24px;\n}\n\n// Stagger.\n//\n// Specificity is load-bearing twice over. Core zeroes the margin of every grid\n// child with `.is-layout-grid > :is(*, div)`, which scores (0,1,1); these rules\n// score (0,3,0) — two classes plus :nth-child — so they win. And the notes\n// themselves restrict their margin support to the bottom edge, so no inline\n// top margin can cancel a stagger the way it could when the offset lived on the\n// child.\n//\n// Bounded at 8 because the rules are enumerated, not computed — CSS cannot do\n// arithmetic on a :nth-child index. A ninth note simply sits flush, which\n// degrades quietly rather than breaking the row.\n@for $i from 1 through 8 {\n  .brandy-pinned-notes.is-stagger-descending > :nth-child(#{$i}) {\n    margin-top: calc(var(--notes-stagger-step, 20px) * #{$i - 1});\n  }\n}\n\n.brandy-pinned-notes.is-stagger-alternating > :nth-child(even) {\n  margin-top: var(--notes-stagger-step, 20px);\n}\n\n// Flatten once the cards stop sitting side by side — a descending stair only\n// reads as intentional across a wide multi-column row. The notes keep their\n// tilt, which is the character of the thing and costs nothing when stacked.\n//\n// (0,3,0) to match the rules above, and later in the file so it wins the tie.\n// Resetting margin rather than --notes-stagger-step is deliberate: render.php\n// writes that custom property inline, and inline beats any stylesheet\n// declaration regardless of the media query.\n@media (max-width: 768px) {\n  .brandy-pinned-notes.brandy-pinned-notes > :nth-child(n) {\n    margin-top: 0;\n  }\n}\n\n// Collapse the columns.\n//\n// Core compiles a grid layout's `columnCount` to a fixed `repeat(4, …)` with no\n// media query behind it, so without this a four-column row is still four columns\n// at 390px — cards about 70px wide, which is unusable. Core has no concept of\n// collapsing it.\n//\n// The theme's GridResponsiveLayout does solve this, but only for blocks on its\n// `$supported_blocks` allowlist and only once an author has set per-viewport\n// values, so it cannot be what makes a freshly inserted block correct. These\n// defaults do that, and they lose cleanly to that mechanism if this block is\n// ever added to it — its rules carry !important.\n//\n// Doubled class scores (0,2,0), which clears core's single-class layout\n// container rule at (0,1,0) without needing !important of our own.\n@media (max-width: 768px) {\n  .brandy-pinned-notes.brandy-pinned-notes {\n    grid-template-columns: repeat(2, minmax(0, 1fr));\n  }\n}\n\n@media (max-width: 480px) {\n  .brandy-pinned-notes.brandy-pinned-notes {\n    grid-template-columns: minmax(0, 1fr);\n  }\n}\n"],"names":[],"sourceRoot":""}