@justai/cuts 0.70.0 → 0.71.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.
- package/package.json +1 -1
- package/src/Segmented.astro +9 -1
package/package.json
CHANGED
package/src/Segmented.astro
CHANGED
|
@@ -126,8 +126,16 @@ const on = value && options.some((o) => o.value === value) ? value : options[0]?
|
|
|
126
126
|
this is what makes it true for the eye. */
|
|
127
127
|
isolation: isolate;
|
|
128
128
|
}
|
|
129
|
+
/* queries: segmented control height · 44px touch target · the segments are too small
|
|
130
|
+
TWO SIZES, AND THE DIFFERENCE IS WHAT THE CONTROL IS.
|
|
131
|
+
`full` is a VIEW'S OWN SWITCH — a thumb's first target on the screen, so it meets the fleet's
|
|
132
|
+
44px like every row and every action does. `inline` is a TOOLBAR CHIP, sitting among other
|
|
133
|
+
chrome at chrome's size; forcing 44 there would make a toolbar taller than its content, which
|
|
134
|
+
is why iOS ships its own segmented controls shorter in exactly that position.
|
|
135
|
+
Found by a consumer's spec measuring 33px where its page promised 44 — a number the component
|
|
136
|
+
should have owned rather than each page discovering separately. */
|
|
129
137
|
.jseg[data-width="full"] { display: flex; width: 100%; }
|
|
130
|
-
.jseg[data-width="full"] .jseg-item { flex: 1; }
|
|
138
|
+
.jseg[data-width="full"] .jseg-item { flex: 1; min-height: 44px; }
|
|
131
139
|
|
|
132
140
|
.jseg-item {
|
|
133
141
|
box-sizing: border-box;
|