You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The toggle button on the extreme right of the page gets truncated or half-hidden when the chat header text is long in total character size (as shown in the screenshot).
Editing the chat title does not support special characters. Clicking the checkbox after editing gives an error message: "Description can only contain alphanumeric characters and spaces."
Once the user selects the model and the initial process starts, the chat modal should collapse by default. Since the model has already been selected, a collapsed view would provide more free screen real estate.
Go to the relevant page in the application where the chat header appears.
Create or edit a chat header with a long title.
Observe the UI issue where the toggle button on the right is truncated.
Attempt to edit the chat title with special characters (e.g., @, #, !) and save the changes using the checkbox.
Note the error message displayed.
Expected behavior
The toggle button should remain fully visible, even when the chat header text is long.
The chat title should allow the use of special characters.
Screen Recording / Screenshot
Issue 1 :
Issue 2 :
_Issue 3_a : Uncollapsed View ❌
_Issue 3_b : Collapsed View ✅
Platform
OS: Windows 10
Browser: Chrome Canary
Device: Laptop
Provider Used
Google
Model Used
Gemini exp-1121
Additional context
This issue may impact user experience significantly for applications with long chat titles.
Consider implementing wrapping or ellipses (...) for long text and allowing special characters in titles for flexibility.
The text was updated successfully, but these errors were encountered:
champ2050
changed the title
Minor Bugs: Chat Header UI Truncation and Special Character Restriction in Title Edit
### Minor Bugs/Fixes: Chat Header UI Truncation and Special Character Restriction in Title Edit
Dec 8, 2024
After I studied this code the issue is in the main prompt to the LLM where it says not to use special characters due to the limitations of the WebContainer and WebAssembly. This is why I think we need to make this project run in a VM.
After I studied this code the issue is in the main prompt to the LLM where it says not to use special characters due to the limitations of the WebContainer and WebAssembly. This is why I think we need to make this project run in a VM.
running the project in a VM requires either hosting person to have rent a VM, which is costly.. and if you are self hosting locally the system and all the environments needs to be setup before you can do any work. not many people knows how to do that. and its different for each OS
web container runs on user's local system, and it can run even on mobile and tablet devices, which is a plus.
it has limitations on what languages it can do but for front end application nodejs is what everyone needs
we might add a local option in future but not in the new future.
Describe the bug
"Description can only contain alphanumeric characters and spaces."
Link to the Bolt URL that caused the error
http://localhost:5173/
Steps to reproduce
@
,#
,!
) and save the changes using the checkbox.Expected behavior
Screen Recording / Screenshot
Issue 1 :
Issue 2 :
_Issue 3_a : Uncollapsed View ❌
_Issue 3_b : Collapsed View ✅
Platform
Provider Used
Google
Model Used
Gemini exp-1121
Additional context
...
) for long text and allowing special characters in titles for flexibility.The text was updated successfully, but these errors were encountered: