@apliteni/apliteni-ui 0.59.0 → 0.61.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/react/README.md +34 -5
- package/react/dist/index.css +4 -0
- package/react/dist/index.d.ts +40 -4
- package/react/dist/index.js +272 -224
- package/src/styles/input.css +14 -0
package/src/styles/input.css
CHANGED
|
@@ -69,6 +69,20 @@
|
|
|
69
69
|
.ui-textarea.is-invalid { border-color: var(--pink); }
|
|
70
70
|
/* Invalid fields keep the shared focus indicator; their border carries the error. */
|
|
71
71
|
|
|
72
|
+
/* A search field with a value gets the browser's own clear button, and the
|
|
73
|
+
browser paints it — near-black on the light field, white on the dark one,
|
|
74
|
+
beside the kit's --muted magnifier. Two glyphs, and only one answers to a
|
|
75
|
+
token. .ui-select refuses UA chrome for the same reason, hand-drawing its
|
|
76
|
+
chevron per theme; and the vanilla search specimen is a text input with a
|
|
77
|
+
`search` glyph and no clear button, so a field without one is what the
|
|
78
|
+
design already says. Measured in Chromium; Firefox draws nothing here and
|
|
79
|
+
Edge is untested.
|
|
80
|
+
why: docs/specification.md#colour-and-contrast */
|
|
81
|
+
.ui-input[type="search"]::-webkit-search-cancel-button {
|
|
82
|
+
appearance: none;
|
|
83
|
+
display: none;
|
|
84
|
+
}
|
|
85
|
+
|
|
72
86
|
/* Input with a leading icon / adornment */
|
|
73
87
|
.ui-input-group { position: relative; display: flex; align-items: center; }
|
|
74
88
|
.ui-input-group .ui-input { padding-left: 42px; }
|