@apliteni/apliteni-ui 0.78.0 → 0.80.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -27,6 +27,11 @@
27
27
  /* 44 − 24: two zones fit between two of the smallest marks the kit draws. */
28
28
  --tap-gap: var(--space-5, 20px);
29
29
 
30
+ /* For a container of BORDERED controls at the smallest mark: `100%` on the
31
+ layer is the padding box, so one of those measures two less there and
32
+ --tap-gap stops its layer short. The floor, less that box. */
33
+ --tap-gap-bordered: calc(var(--tap-min) - var(--tap-aa) + 2px);
34
+
30
35
  /* Clear space to the nearest neighbour, declared by the container that knows
31
36
  its own gap; a zone takes half on each side.
32
37
 
@@ -50,7 +55,12 @@
50
55
  .ui-toast__action,
51
56
  .ui-drawer__close,
52
57
  .ui-snippet__copy,
53
- .ui-footer__social
58
+ .ui-footer__social,
59
+ /* Already relative in react/src/DatePicker.css — restated because this
60
+ gate reads the kit's own sheets and cannot see that one, and a carrier
61
+ whose containing block it cannot find is a layer that measures against
62
+ whatever ancestor happens to be positioned. */
63
+ .ui-datepicker__opt
54
64
  ) { position: relative; }
55
65
 
56
66
  /* The layer: centred, transparent, sized to the floor, clamped to half the
@@ -64,7 +74,8 @@
64
74
  .ui-drawer__close,
65
75
  .ui-snippet__copy,
66
76
  .ui-footer__social,
67
- .ui-switch
77
+ .ui-switch,
78
+ .ui-datepicker__opt
68
79
  )::after {
69
80
  content: "";
70
81
  position: absolute;
@@ -164,6 +175,26 @@
164
175
  --tap-clear-y: var(--tap-gap);
165
176
  }
166
177
 
178
+ /* `.ui-seg`'s shape at seven columns: cells packed across — that tight track
179
+ IS the control — opening down, where the sheet has the room. The rows
180
+ inherit both clearances. React-only, so the browser half below reports no
181
+ subject and react/src/DatePicker.test.tsx holds these declarations. */
182
+ .ui-datepicker__grid {
183
+ row-gap: var(--tap-gap) !important;
184
+ --tap-clear-x: var(--space-1, 4px);
185
+ --tap-clear-y: var(--tap-gap);
186
+ }
187
+
188
+ /* Neither axis is opened: the room is already there, a hundred pixels to the
189
+ caption and twelve to the grid, which is how `.ui-tabs__list` declares its
190
+ own. The bordered step, because both controls are bordered at --tap-aa. */
191
+ .ui-datepicker__head { --tap-clear-x: var(--tap-gap-bordered); --tap-clear-y: var(--tap-gap-bordered); }
192
+
193
+ /* The row scrolls, so its own block padding is the clearance — anything
194
+ past the chip is clipped rather than hit. The chips are already wider
195
+ than the floor, so the gap across stays the kit's. */
196
+ .ui-datepicker__presets { --tap-clear-x: var(--space-1, 4px); --tap-clear-y: var(--tap-gap-bordered); }
197
+
167
198
  /* Both ways: fixed squares cannot overflow the way labels can, and a drawer
168
199
  header spends its column gap on the title. Not the accent picker — its
169
200
  swatches are on no carrier list, so opening it bought no reach. */