@hsu-react/ui 2.4.6 → 2.4.8

package/es/components/Chat/ChatInput/index.d.ts

@@ -51,6 +51,16 @@ export interface ChatInputProps {
     onFileInterceptClick?: (e: React.MouseEvent<HTMLSpanElement>) => void;
     buttonGroup?: ButtonProps[];
     uploadEnabled?: boolean;
+    /**
+     * Disable sending. The send button turns disabled and Enter no longer submits;
+     * the textarea stays editable so a half-typed message is never lost.
+     *
+     * The component already disables the send button during its own uploads
+     * (`isUpload`), but consumers that run their own upload flow
+     * (`uploadEnabled={false}`) had no way in: they could only intercept `onSend`
+     * and pop a warning, leaving the button looking perfectly clickable.
+     */
+    disabled?: boolean;
 }
 declare const ChatInput: React.FC<ChatInputProps>;
 export default ChatInput;

package/es/components/Chat/ChatInput/index.js

@@ -43,7 +43,9 @@ var ChatInput = function ChatInput(props) {
     onFileInterceptClick = props.onFileInterceptClick,
     buttonGroup = props.buttonGroup,
     _props$uploadEnabled = props.uploadEnabled,
-    uploadEnabled = _props$uploadEnabled === void 0 ? true : _props$uploadEnabled;
+    uploadEnabled = _props$uploadEnabled === void 0 ? true : _props$uploadEnabled,
+    _props$disabled = props.disabled,
+    disabled = _props$disabled === void 0 ? false : _props$disabled;
   var _useState = useState(""),
     _useState2 = _slicedToArray(_useState, 2),
     value = _useState2[0],
@@ -145,6 +147,9 @@ var ChatInput = function ChatInput(props) {
 
   // Handle sending
   var handleSend = function handleSend() {
+    if (disabled) {
+      return;
+    }
     if (value.trim() !== "") {
       setValue("");
       onSend === null || onSend === void 0 || onSend(value);
@@ -239,7 +244,7 @@ var ChatInput = function ChatInput(props) {
             value: value,
             onSend: handleSend,
             sendIcon: sendIcon,
-            disabled: isUpload
+            disabled: isUpload || disabled
           })
         })]
       })]

package/es/components/Input/index.module.scss

@@ -1,8 +1,12 @@
 .antdInput {
   width: 100%;
-  height: 100%;
-  // When the parent has no set height (height:100% resolves to auto), ensure a minimum height so the input is not squashed;
-  // the inner .ant-input-wrapper / .ant-input inherit this value via min-height: inherit.
+  // The control height is a floor, not `height: 100%` — see the long note in
+  // `Select/index.module.scss`. Same failure: under a flex item stretched by a taller
+  // sibling, `height: 100%` inflates the input to the item's whole content box.
+  //
+  // The inner `height: 100%` rules below stay: when this root *is* stretched (as a flex
+  // child, or because the app asked for it), they propagate that height inward. They
+  // resolve to `auto` otherwise and fall back to `min-height: inherit`.
   min-height: var(--vita-control-height);
 
   :global(.ant-input-clear-icon) {

package/es/components/Select/TreeSelect/index.module.scss

@@ -4,7 +4,10 @@
   --tree-switcher-gap: 0px;
 
   width: 100%;
-  height: 100%;
+  // Control height as a floor, not `height: 100%` — same reason as `Select` (see the
+  // note there). TreeSelect had no `min-height` at all because `height: 100%` was doing
+  // that job by accident; dropping one without adding the other would collapse it.
+  min-height: var(--vita-control-height);
 
   // CF style: outlined input control that follows appearance switching.
   //

package/es/components/Select/index.module.scss

@@ -5,9 +5,24 @@
   align-items: center;
 
   width: 100%;
-  height: 100%;
-  // When the parent has no explicit height (height:100% resolves to auto), guarantee a min height
-  // consistent with Input and other form controls, so it is neither squashed nor mis-sized in search rows.
+  // The control height is a floor, not `height: 100%`.
+  //
+  // `height: 100%` looks harmless because it resolves to `auto` under an auto-height
+  // parent — but the moment the parent has a *definite* height the control inflates to
+  // fill it, and the most common way a parent acquires one is by accident: a flex item
+  // stretched by a taller sibling. A card holding `<label> <Select> <hint>` where the
+  // hint wraps to two lines is enough — the Select swells to the card's whole content
+  // box (measured: 102px for a 32px control) and covers the label and the hint.
+  //
+  // This bit hsu-ui itself: `ChainGraph/SearchSelect` has to park the Select in a
+  // fixed 32px box, "preventing the Select root's height:100% from resolving against
+  // the graph and being stretched to the full graph height". Consumers hit it too and
+  // reach for the same wrapper, which is a workaround for a default that is wrong.
+  //
+  // Filling a deliberately sized parent still works without the declaration: as a flex
+  // child the default `align-self: stretch` fills the cross axis, and the inner
+  // `height: 100%` rules below then resolve against a genuinely definite height.
+  // A block parent that really wants a taller control can still say `height: 100%`.
   min-height: var(--vita-control-height);
   padding: 0px 11px;
 
@@ -118,7 +133,16 @@
     align-items: center;
 
     width: 100%;
-    height: 100%;
+    // 撑满外壳用 align-self，不用 height: 100%。
+    //
+    // 外壳 `.select` 的高度是 `min-height` 撑出来的、`height` 仍是 auto，
+    // 百分比高度对着 auto 解析不出东西 —— 这一层会缩回内容高（实测 22px，
+    // 而外壳是 32px），上下各多出 5px 点不动的死区：看着是个 32px 的下拉框，
+    // 边缘一圈却没有反应。
+    //
+    // 外壳是 flex 且 align-items: center，所以这里要显式 stretch；
+    // 前后缀图标不受影响，它们该保持居中
+    align-self: stretch;
     margin: 0px !important;
 
     border-radius: inherit;

package/lib/components/Chat/ChatInput/index.d.ts

@@ -51,6 +51,16 @@ export interface ChatInputProps {
     onFileInterceptClick?: (e: React.MouseEvent<HTMLSpanElement>) => void;
     buttonGroup?: ButtonProps[];
     uploadEnabled?: boolean;
+    /**
+     * Disable sending. The send button turns disabled and Enter no longer submits;
+     * the textarea stays editable so a half-typed message is never lost.
+     *
+     * The component already disables the send button during its own uploads
+     * (`isUpload`), but consumers that run their own upload flow
+     * (`uploadEnabled={false}`) had no way in: they could only intercept `onSend`
+     * and pop a warning, leaving the button looking perfectly clickable.
+     */
+    disabled?: boolean;
 }
 declare const ChatInput: React.FC<ChatInputProps>;
 export default ChatInput;

package/lib/components/Chat/ChatInput/index.js

@@ -34,7 +34,8 @@ const ChatInput = props => {
     wrapperClassName,
     onFileInterceptClick,
     buttonGroup,
-    uploadEnabled = true
+    uploadEnabled = true,
+    disabled = false
   } = props;
   const [value, setValue] = (0, _react.useState)("");
   const [isUpload, setIsUpload] = (0, _react.useState)(false);
@@ -111,6 +112,9 @@ const ChatInput = props => {
 
   // Handle sending
   const handleSend = () => {
+    if (disabled) {
+      return;
+    }
     if (value.trim() !== "") {
       setValue("");
       onSend?.(value);
@@ -198,7 +202,7 @@ const ChatInput = props => {
             value: value,
             onSend: handleSend,
             sendIcon: sendIcon,
-            disabled: isUpload
+            disabled: isUpload || disabled
           })
         })]
       })]

package/lib/components/Input/index.module.scss

@@ -1,8 +1,12 @@
 .antdInput {
   width: 100%;
-  height: 100%;
-  // When the parent has no set height (height:100% resolves to auto), ensure a minimum height so the input is not squashed;
-  // the inner .ant-input-wrapper / .ant-input inherit this value via min-height: inherit.
+  // The control height is a floor, not `height: 100%` — see the long note in
+  // `Select/index.module.scss`. Same failure: under a flex item stretched by a taller
+  // sibling, `height: 100%` inflates the input to the item's whole content box.
+  //
+  // The inner `height: 100%` rules below stay: when this root *is* stretched (as a flex
+  // child, or because the app asked for it), they propagate that height inward. They
+  // resolve to `auto` otherwise and fall back to `min-height: inherit`.
   min-height: var(--vita-control-height);
 
   :global(.ant-input-clear-icon) {

package/lib/components/Select/TreeSelect/index.module.scss

@@ -4,7 +4,10 @@
   --tree-switcher-gap: 0px;
 
   width: 100%;
-  height: 100%;
+  // Control height as a floor, not `height: 100%` — same reason as `Select` (see the
+  // note there). TreeSelect had no `min-height` at all because `height: 100%` was doing
+  // that job by accident; dropping one without adding the other would collapse it.
+  min-height: var(--vita-control-height);
 
   // CF style: outlined input control that follows appearance switching.
   //

package/lib/components/Select/index.module.scss

@@ -5,9 +5,24 @@
   align-items: center;
 
   width: 100%;
-  height: 100%;
-  // When the parent has no explicit height (height:100% resolves to auto), guarantee a min height
-  // consistent with Input and other form controls, so it is neither squashed nor mis-sized in search rows.
+  // The control height is a floor, not `height: 100%`.
+  //
+  // `height: 100%` looks harmless because it resolves to `auto` under an auto-height
+  // parent — but the moment the parent has a *definite* height the control inflates to
+  // fill it, and the most common way a parent acquires one is by accident: a flex item
+  // stretched by a taller sibling. A card holding `<label> <Select> <hint>` where the
+  // hint wraps to two lines is enough — the Select swells to the card's whole content
+  // box (measured: 102px for a 32px control) and covers the label and the hint.
+  //
+  // This bit hsu-ui itself: `ChainGraph/SearchSelect` has to park the Select in a
+  // fixed 32px box, "preventing the Select root's height:100% from resolving against
+  // the graph and being stretched to the full graph height". Consumers hit it too and
+  // reach for the same wrapper, which is a workaround for a default that is wrong.
+  //
+  // Filling a deliberately sized parent still works without the declaration: as a flex
+  // child the default `align-self: stretch` fills the cross axis, and the inner
+  // `height: 100%` rules below then resolve against a genuinely definite height.
+  // A block parent that really wants a taller control can still say `height: 100%`.
   min-height: var(--vita-control-height);
   padding: 0px 11px;
 
@@ -118,7 +133,16 @@
     align-items: center;
 
     width: 100%;
-    height: 100%;
+    // 撑满外壳用 align-self，不用 height: 100%。
+    //
+    // 外壳 `.select` 的高度是 `min-height` 撑出来的、`height` 仍是 auto，
+    // 百分比高度对着 auto 解析不出东西 —— 这一层会缩回内容高（实测 22px，
+    // 而外壳是 32px），上下各多出 5px 点不动的死区：看着是个 32px 的下拉框，
+    // 边缘一圈却没有反应。
+    //
+    // 外壳是 flex 且 align-items: center，所以这里要显式 stretch；
+    // 前后缀图标不受影响，它们该保持居中
+    align-self: stretch;
     margin: 0px !important;
 
     border-radius: inherit;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hsu-react/ui",
-  "version": "2.4.6",
+  "version": "2.4.8",
   "description": "一套基于 React + Ant Design 的中后台业务组件库",
   "license": "MIT",
   "type": "module",

package/src/components/Chat/ChatInput/index.tsx

@@ -67,6 +67,16 @@ export interface ChatInputProps {
   onFileInterceptClick?: (e: React.MouseEvent<HTMLSpanElement>) => void;
   buttonGroup?: ButtonProps[];
   uploadEnabled?: boolean;
+  /**
+   * Disable sending. The send button turns disabled and Enter no longer submits;
+   * the textarea stays editable so a half-typed message is never lost.
+   *
+   * The component already disables the send button during its own uploads
+   * (`isUpload`), but consumers that run their own upload flow
+   * (`uploadEnabled={false}`) had no way in: they could only intercept `onSend`
+   * and pop a warning, leaving the button looking perfectly clickable.
+   */
+  disabled?: boolean;
 }
 
 const ChatInput: React.FC<ChatInputProps> = (props) => {
@@ -88,6 +98,7 @@ const ChatInput: React.FC<ChatInputProps> = (props) => {
     onFileInterceptClick,
     buttonGroup,
     uploadEnabled = true,
+    disabled = false,
   } = props;
 
   const [value, setValue] = useState<string>("");
@@ -178,6 +189,9 @@ const ChatInput: React.FC<ChatInputProps> = (props) => {
 
   // Handle sending
   const handleSend = () => {
+    if (disabled) {
+      return;
+    }
     if (value.trim() !== "") {
       setValue("");
       onSend?.(value);
@@ -275,7 +289,7 @@ const ChatInput: React.FC<ChatInputProps> = (props) => {
                 value={value}
                 onSend={handleSend}
                 sendIcon={sendIcon}
-                disabled={isUpload}
+                disabled={isUpload || disabled}
               />
             )}
           </>

package/src/components/Input/index.module.scss

@@ -1,8 +1,12 @@
 .antdInput {
   width: 100%;
-  height: 100%;
-  // When the parent has no set height (height:100% resolves to auto), ensure a minimum height so the input is not squashed;
-  // the inner .ant-input-wrapper / .ant-input inherit this value via min-height: inherit.
+  // The control height is a floor, not `height: 100%` — see the long note in
+  // `Select/index.module.scss`. Same failure: under a flex item stretched by a taller
+  // sibling, `height: 100%` inflates the input to the item's whole content box.
+  //
+  // The inner `height: 100%` rules below stay: when this root *is* stretched (as a flex
+  // child, or because the app asked for it), they propagate that height inward. They
+  // resolve to `auto` otherwise and fall back to `min-height: inherit`.
   min-height: var(--vita-control-height);
 
   :global(.ant-input-clear-icon) {

package/src/components/Select/TreeSelect/index.module.scss

@@ -4,7 +4,10 @@
   --tree-switcher-gap: 0px;
 
   width: 100%;
-  height: 100%;
+  // Control height as a floor, not `height: 100%` — same reason as `Select` (see the
+  // note there). TreeSelect had no `min-height` at all because `height: 100%` was doing
+  // that job by accident; dropping one without adding the other would collapse it.
+  min-height: var(--vita-control-height);
 
   // CF style: outlined input control that follows appearance switching.
   //

package/src/components/Select/index.module.scss

@@ -5,9 +5,24 @@
   align-items: center;
 
   width: 100%;
-  height: 100%;
-  // When the parent has no explicit height (height:100% resolves to auto), guarantee a min height
-  // consistent with Input and other form controls, so it is neither squashed nor mis-sized in search rows.
+  // The control height is a floor, not `height: 100%`.
+  //
+  // `height: 100%` looks harmless because it resolves to `auto` under an auto-height
+  // parent — but the moment the parent has a *definite* height the control inflates to
+  // fill it, and the most common way a parent acquires one is by accident: a flex item
+  // stretched by a taller sibling. A card holding `<label> <Select> <hint>` where the
+  // hint wraps to two lines is enough — the Select swells to the card's whole content
+  // box (measured: 102px for a 32px control) and covers the label and the hint.
+  //
+  // This bit hsu-ui itself: `ChainGraph/SearchSelect` has to park the Select in a
+  // fixed 32px box, "preventing the Select root's height:100% from resolving against
+  // the graph and being stretched to the full graph height". Consumers hit it too and
+  // reach for the same wrapper, which is a workaround for a default that is wrong.
+  //
+  // Filling a deliberately sized parent still works without the declaration: as a flex
+  // child the default `align-self: stretch` fills the cross axis, and the inner
+  // `height: 100%` rules below then resolve against a genuinely definite height.
+  // A block parent that really wants a taller control can still say `height: 100%`.
   min-height: var(--vita-control-height);
   padding: 0px 11px;
 
@@ -118,7 +133,16 @@
     align-items: center;
 
     width: 100%;
-    height: 100%;
+    // 撑满外壳用 align-self，不用 height: 100%。
+    //
+    // 外壳 `.select` 的高度是 `min-height` 撑出来的、`height` 仍是 auto，
+    // 百分比高度对着 auto 解析不出东西 —— 这一层会缩回内容高（实测 22px，
+    // 而外壳是 32px），上下各多出 5px 点不动的死区：看着是个 32px 的下拉框，
+    // 边缘一圈却没有反应。
+    //
+    // 外壳是 flex 且 align-items: center，所以这里要显式 stretch；
+    // 前后缀图标不受影响，它们该保持居中
+    align-self: stretch;
     margin: 0px !important;
 
     border-radius: inherit;