xtermjs/xterm.js

Inconsistent term.onData Event Behavior Between iOS and Android in React Native WebView Terminal

Open

#5,108 建立於 2024年7月21日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)TypeScript (16,196 star) (1,574 fork)batch import
area/mobilehelp wantedtype/enhancement

描述

Inconsistent term.onData Event Behavior Between iOS and Android in React Native WebView Terminal

Expected Behavior: The term.onData event should trigger immediately on every key press in both iOS and Android platforms.

Actual Behavior:

iOS: The term.onData event fires immediately on every key press, as expected. Android: The term.onData event only fires when the Enter key is pressed twice.

Additional Information:

I've tried different configurations and approaches, but the issue persists only on Android. It seems like the data from the keyboard input is being buffered and only sent after pressing Enter twice.

Could anyone provide insights or solutions to ensure consistent behavior of the term.onData event on both iOS and Android platforms?

Details

  • Browser and browser version:
  • OS version Mozilla/5.0 (Linux; Android 14; sdk_gphone64_x86_64 Build/UE1A.230829.036.A1; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/113.0.5672.136 Mobile Safari/537.36
  • xterm.js version: 5.5.0

Steps to reproduce

  1. clone the repo https://github.com/raghulkrishna/xtermtest
  2. cd xtermtest
  3. npm i
  4. npx expo run:android/ios

貢獻者指南

技術棧
typescriptreact nativeandroidios
領域
mobile
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
React NativeAndroid WebViewxterm.js event handling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the Android WebView implementation to understand why term.onData event is buffered. Compare with iOS implementation to identify the platform specific code that causes the delay. Focus on the keyboard input handling in the React Native WebView component and how events are forwarded to xterm.js. Check if there is a known workaround or configuration to bypass the double enter issue.