-
-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
[Bug] 对话复选框按钮被遮挡 #6759
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
@RAiNY7Study 你好!我是Dosu,我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。我会在等待人类维护者的过程中帮助你。 The issue you're experiencing with the checkbox being obscured in the chat interface might be related to the layout and positioning of UI elements. To address this, you may need to modify the layout or CSS styles to reposition the checkbox. Unfortunately, I couldn't find specific information about the component or styles responsible for rendering checkboxes in the lobe-chat codebase. However, you can start by checking the layout files, such as To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
The issue you're experiencing with the checkbox being obscured in the chat interface might be related to the layout or CSS styles applied to the UI elements. To address this, you can try the following steps:
By making these adjustments, you should be able to reposition the checkbox to avoid it being obscured. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
This issue is closed, If you have any questions, you can comment and reply. |
📦 部署环境
Docker
📦 部署模式
服务端模式(lobe-chat-database 镜像)
📌 软件版本
1.68.3
💻 系统环境
Windows
🌐 浏览器
Edge
🐛 问题描述
由于搜索引用的内容过多,导致的该聊天对话框的复选框被遮盖,无法操作,如下图所示

📷 复现步骤
No response
🚦 期望结果
可以将这个复选框,换个位置
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: