fix(frontend): improve chat input status indicator responsiveness #11202
Conversation
|
Hi @YakshithK, I found an issue when testing the PR locally. issue: When accessing the conversation page on a large screen, the text does not remain on a single line but instead wraps into two lines. Subsequently, when the chat window is resized to a smaller width, the display issue persists with little noticeable difference from the initial state. For further clarification, please refer to the video provided below. issue.mov |
|
Thanks for catching this! I updated the CSS to ensure the status text stays single-line on large screens and adapts properly when resizing. Let me know if you catch anything else! |
|
Thank you! |
Co-authored-by: openhands <openhands@all-hands.dev>
Co-authored-by: openhands <openhands@all-hands.dev>
…s-AI#11209) Co-authored-by: openhands <openhands@all-hands.dev>
Head branch was pushed to by a user without write access
YakshithK
force-pushed
the
fix/chat-input-ui
branch
from
53eff77 to
cc0355f
Compare
|
Hi all, the Python test is failing on Linux, but I believe it’s unrelated to my frontend changes. Let me know if you want me to look into it, otherwise this PR is ready to merge. |
7 participants
End-user friendly description of the problem this fixes or functionality this introduces.
This fix improves the responsiveness of the chat input status indicator in OpenHands, ensuring it displays correctly even when the window size is reduced. This resolves the UI issue where the indicator layout broke or appeared incorrectly on smaller screens.
Summarize what the PR does, explaining any non-trivial design decisions.
This PR adjusts the styling and layout of the
waiting-for-runtime-message.tsxcomponent to handle various viewport sizes gracefully. The changes involve CSS adjustments and minor component structure modifications to improve adaptability without affecting other UI elements. The solution ensures consistent behavior across devices and window sizes while maintaining performance and accessibility.Link of any specific issues this addresses:
Fixes #11117