UNPKG

@blueprintjs/core

Version:
101 lines 5.91 kB
/* ! * (c) Copyright 2023 Palantir Technologies Inc. All rights reserved. */ import * as React from "react"; /** * The amount of time (in milliseconds) which the input will wait after a compositionEnd event before * unlocking its state value for external updates via props. See `handleCompositionEnd` for more details. */ export var ASYNC_CONTROLLABLE_VALUE_COMPOSITION_END_DELAY = 10; /* * A hook to workaround the following [React bug](https://github.com/facebook/react/issues/3926). * This bug is reproduced when an input receives CompositionEvents * (for example, through IME composition) and has its value prop updated asychronously. * This might happen if a component chooses to do async validation of a value * returned by the input's `onChange` callback. */ export function useAsyncControllableValue(props) { var onCompositionStart = props.onCompositionStart, onCompositionEnd = props.onCompositionEnd, propValue = props.value, onChange = props.onChange; // The source of truth for the input value. This is not updated during IME composition. // It may be updated by a parent component. var _a = React.useState(propValue), value = _a[0], setValue = _a[1]; // The latest input value, which updates during IME composition. var _b = React.useState(propValue), nextValue = _b[0], setNextValue = _b[1]; // Whether we are in the middle of a composition event. var _c = React.useState(false), isComposing = _c[0], setIsComposing = _c[1]; // Whether there is a pending update we are expecting from a parent component. var _d = React.useState(false), hasPendingUpdate = _d[0], setHasPendingUpdate = _d[1]; var cancelPendingCompositionEnd = React.useRef(); var handleCompositionStart = React.useCallback(function (event) { var _a; (_a = cancelPendingCompositionEnd.current) === null || _a === void 0 ? void 0 : _a.call(cancelPendingCompositionEnd); setIsComposing(true); onCompositionStart === null || onCompositionStart === void 0 ? void 0 : onCompositionStart(event); }, [onCompositionStart]); // creates a timeout which will set `isComposing` to false after a delay // returns a function which will cancel the timeout if called before it fires var createOnCancelPendingCompositionEnd = React.useCallback(function () { var timeoutId = window.setTimeout(function () { return setIsComposing(false); }, ASYNC_CONTROLLABLE_VALUE_COMPOSITION_END_DELAY); return function () { return window.clearTimeout(timeoutId); }; }, []); var handleCompositionEnd = React.useCallback(function (event) { // In some non-latin languages, a keystroke can end a composition event and immediately afterwards start another. // This can lead to unexpected characters showing up in the text input. In order to circumvent this problem, we // use a timeout which creates a delay which merges the two composition events, creating a more natural and predictable UX. // `this.state.nextValue` will become "locked" (it cannot be overwritten by the `value` prop) until a delay (10ms) has // passed without a new composition event starting. cancelPendingCompositionEnd.current = createOnCancelPendingCompositionEnd(); onCompositionEnd === null || onCompositionEnd === void 0 ? void 0 : onCompositionEnd(event); }, [createOnCancelPendingCompositionEnd, onCompositionEnd]); var handleChange = React.useCallback(function (event) { var targetValue = event.target.value; setNextValue(targetValue); onChange === null || onChange === void 0 ? void 0 : onChange(event); }, [onChange]); // don't derive anything from props if: // - in uncontrolled mode, OR // - currently composing, since we'll do that after composition ends var shouldDeriveFromProps = !(isComposing || propValue === undefined); if (shouldDeriveFromProps) { var userTriggeredUpdate = nextValue !== value; if (userTriggeredUpdate && propValue === nextValue) { // parent has processed and accepted our update setValue(propValue); setHasPendingUpdate(false); } else if (userTriggeredUpdate && propValue === value) { // we have sent the update to our parent, but it has not been processed yet. just wait. // DO NOT set nextValue here, since that will temporarily render a potentially stale controlled value, // causing the cursor to jump once the new value is accepted if (!hasPendingUpdate) { // make sure to setState only when necessary to avoid infinite loops setHasPendingUpdate(true); } } else if (userTriggeredUpdate && propValue !== value) { // accept controlled update overriding user action setValue(propValue); setNextValue(propValue); setHasPendingUpdate(false); } else if (!userTriggeredUpdate) { // accept controlled update, could be confirming or denying user action if (value !== propValue || hasPendingUpdate) { // make sure to setState only when necessary to avoid infinite loops setValue(propValue); setNextValue(propValue); setHasPendingUpdate(false); } } } return { onChange: handleChange, onCompositionEnd: handleCompositionEnd, onCompositionStart: handleCompositionStart, // render the pending value even if it is not confirmed by a parent's async controlled update // so that the cursor does not jump to the end of input as reported in // https://github.com/palantir/blueprint/issues/4298 value: isComposing || hasPendingUpdate ? nextValue : value, }; } //# sourceMappingURL=useAsyncControllableValue.js.map