Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Various Synchronization and Display Issues in Components #11849

Closed
5 tasks done
Woo0ood opened this issue Dec 19, 2024 · 0 comments · Fixed by #12349, #12350, #12351 or #12352
Closed
5 tasks done

Fix Various Synchronization and Display Issues in Components #11849

Woo0ood opened this issue Dec 19, 2024 · 0 comments · Fixed by #12349, #12350, #12351 or #12352
Assignees
Labels
🐞 bug Something isn't working

Comments

@Woo0ood
Copy link
Contributor

Woo0ood commented Dec 19, 2024

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Several issues have been identified that need to be addressed:

  1. AutomaticRes Component Synchronization Issue: The opening remarks generated by the AutomaticRes component are not automatically synchronized with the current orchestration state. Users need to save the changes for them to take effect, which disrupts workflow.

  2. WeightedScore Component Style Issue: The WeightedScore component slightly overlaps with other elements, affecting the visual layout and user interface.

  3. Echarts and Markdown Display Issue: Echarts charts and Markdown tables are displayed too wide in conversations, causing layout problems within the message window.

  4. Missing i18n Items: The copy image button in the image preview component is missing i18n items, leading to localization issues.

  5. Chat Input Area Clearing Issue: The chat input area is cleared after sending a message in response state, which is not the expected behavior. The input content should be retained if the state is in response mode.

  6. Old Replies Display Issue: After regenerating a reply and switching conversations, the old replies are displayed when switching back. The new reply should be displayed immediately without requiring a page refresh.

  7. TextGeneration Input Data Clearing Issue: The TextGeneration component in the text generation application does not correctly reset references when clearing the form. This issue causes old form values to be automatically filled in upon re-entering data. The form references should be correctly reset after clearing to ensure that new input data is not affected by previous values.

These issues need to be fixed to improve the functionality and user experience of the application.

2. Additional context or comments

(Sorry for using the wrong template, but this issue will report and prepare to resolve multiple bugs. We have fixed this or these issues and are ready to submit the PR.)

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment