can't input Chinese Number

[jsonParseTo]

hi,bro:
I have a problem in Chinese typing system, I can't input Chinese Numbers. but when i use english typing system, It's ok.

Details

• Browser and browser version: safari
• OS version: Iphone11 & IOS Version17.1.2 or android
• xterm.js version: 5.5.0

Video

113_1716977019.mp4

Code

import { useState, useRef, useEffect } from 'react';
import { Terminal } from '@xterm/xterm';
import { FitAddon } from '@xterm/addon-fit';
import '@xterm/xterm/css/xterm.css';

function App() {
    const terminalRef = useRef(null);
    const [termInputValue, setTermInputValue] = useState('');

    useEffect(() => {
        terminalRef.current = new Terminal();
        terminalRef.current.loadAddon(new FitAddon());
        terminalRef.current.open(document.getElementById('terminal'))

        terminalRef.current.onKey((e) => {
            const printable = !e.domEvent.altKey && !e.domEvent.altGraphKey && !e.domEvent.ctrlKey && !e.domEvent.metaKey;
            if (e.domEvent.keyCode === 13) {
                terminalRef.current.write('\r\n');
                setTermInputValue('');
            } else if (e.domEvent.keyCode === 8) {
                terminalRef.current.write('\b \b');
                const inputVlaue = termInputValue.substring(0, termInputValue.length - 1);
                setTermInputValue(inputVlaue);
            } else if (printable) {
                terminalRef.current.write(e.key);
                setTermInputValue(termInputValue + e.key);
            }
        });

        terminalRef.current.onData((e) => {
            const reg = new RegExp('[\u4E00-\u9FA5]+');
            if (e.length > 1 || reg.test(e)) {
                terminalRef.current.write(e.replace(/(\r\n)/g, '\n').replace(/(\r)/g, '\n'));
                setTermInputValue(`${termInputValue}${e}`);
            }
        });
    }, [])
    return (
        <div id="terminal" />
    );
}

export default App;

[jerch]

This is most likely caused by the IME or whatever composing trick your keyboard app uses.

Feel free to move it back an issues, if you think it is indeed caused by faulty behavior of xterm.js itself.