slidytabs 0.1.7 → 0.1.8
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/README.md +3 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,7 +11,7 @@ Examples/demo at https://slidytabs.dev
|
|
|
11
11
|
- **`tabs()`**: shadcn `<Tabs />` jump between positions, which can feel abrupt in motion-oriented UIs. A solution should work with Tabs *as-is*, not as a wrapper or replacement.
|
|
12
12
|
|
|
13
13
|
|
|
14
|
-
- **`slider()` / `range()`**:
|
|
14
|
+
- **`slider()` / `range()`**: Sometimes you want the semantics of a radio button or select, with the linearity and tactility of a slider. This comes up often when selecting from small, discrete sets where sliders feel *almost* right, but slightly wrong. Think clothing sizes, days of the week, months, tip amounts, or school grades. [See this UX StackExchange discussion](https://ux.stackexchange.com/questions/122217/what-is-the-best-ui-component-to-make-user-select-a-number-from-small-range-1-1).
|
|
15
15
|
|
|
16
16
|
## Install
|
|
17
17
|
|
|
@@ -116,3 +116,5 @@ range(options?: {
|
|
|
116
116
|
Getting this to work requires some `document.styleSheets` acrobatics, and this is an early release, so edge cases likely exist.
|
|
117
117
|
|
|
118
118
|
Please open issues, especially if your Tabs component works as expected without `slidytabs`, but behaves unexpectedly once `slidytabs` is applied.
|
|
119
|
+
|
|
120
|
+
Sliders can smuggle in unwanted semantics
|