-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Markdown table too wide, scrollbar disappears, data in the latter half not displayed. #15560
Comments
To address the issue of a Markdown table being too wide and causing the scrollbar to disappear in your self-hosted Dify version 1.0.1 environment, you can modify the CSS for the table to ensure it is scrollable. Update the .markdown-body table {
border-spacing: 0;
border-collapse: separate;
display: block;
width: max-content;
max-width: 100%;
overflow: auto; /* Change this line */
border: 1px solid var(--color-divider-regular);
border-radius: 8px;
} This change will allow a scrollbar to appear when the table exceeds the width of its container, enabling users to scroll and view the entire content of the table [1]. 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 |
.markdown-body table { |
Do I need to rebuild the image after making the changes? |
The CSS you've provided is correct for making a Markdown table scrollable horizontally. This will ensure that when the table content exceeds the container's width, a horizontal scrollbar will appear, allowing users to view the entire table content. This approach maintains the table's border and border-radius formatting [1]. 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 |
@omjasoliya @crazywoola |
No, you don’t need to rebuild the image. Simply modifying markdown.scss
and restarting the frontend service should apply the changes. You can try
clearing the browser cache or refreshing the page if the changes don’t
appear immediately
If you want step by step guidance then feel free to ask :)
@dosu
…On Wed, 12 Mar 2025 at 12:12, suntao2015005848 ***@***.***> wrote:
@omjasoliya <https://github.com/omjasoliya> @crazywoola
<https://github.com/crazywoola>
Do I need to rebuild the image if I modify the markdown.scss?
—
Reply to this email directly, view it on GitHub
<#15560 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZV7535G4VKCIWD4VWA2G3D2T7JMNAVCNFSM6AAAAABY2PUYBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJWG4YDIMBUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: suntao2015005848]*suntao2015005848* left a comment
(langgenius/dify#15560)
<#15560 (comment)>
@omjasoliya <https://github.com/omjasoliya> @crazywoola
<https://github.com/crazywoola>
Do I need to rebuild the image if I modify the markdown.scss?
—
Reply to this email directly, view it on GitHub
<#15560 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZV7535G4VKCIWD4VWA2G3D2T7JMNAVCNFSM6AAAAABY2PUYBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJWG4YDIMBUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No, you don't need to rebuild the Docker image after modifying 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 |
I updated the markdown.scss and restarted the docker-web-1, but the format of the markdown table did not take effect. @dosu |
After updating 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 |
may be there is restarting problem have you tried this command?
docker compose restart frontend
…On Wed, 12 Mar 2025 at 13:27, suntao2015005848 ***@***.***> wrote:
I updated the markdown.scss and restarted the docker-web-1, but the format
of the markdown table did not take effect. @dosu <https://github.com/dosu>
—
Reply to this email directly, view it on GitHub
<#15560 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZV7533XQZZDTH4NLFSD3CT2T7SFVAVCNFSM6AAAAABY2PUYBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJWHE3DKOBXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: suntao2015005848]*suntao2015005848* left a comment
(langgenius/dify#15560)
<#15560 (comment)>
I updated the markdown.scss and restarted the docker-web-1, but the format
of the markdown table did not take effect. @dosu <https://github.com/dosu>
—
Reply to this email directly, view it on GitHub
<#15560 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZV7533XQZZDTH4NLFSD3CT2T7SFVAVCNFSM6AAAAABY2PUYBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJWHE3DKOBXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Well, you need to rebuild the frontend image @suntao2015005848 |
Try using the command 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 |
thanks , After rebuilding, it was successful.Executing docker compose restart frontend resulted in an error: no such service: frontend. |
请问一下你是怎么重建的呀,我重建web镜像之后启动还是不可以, 然后修改docker-compose.yml 文件中的web镜像版本 |
Possible Reasons & Fixes: docker compose ps 2️⃣ Missing or Incorrect docker-compose.yml ls docker-compose.yml If it doesn’t exist, navigate to the correct directory. 3️⃣ Docker Compose Version Issue docker-compose restart frontend 4️⃣ Containers Are Not Running docker compose up -d |
1、更改 markdown.scss 2、修改 docker-compose.yml
|
可以了,谢谢你 👍 |
Yes! Based on the steps you've taken, you should now execute: docker compose up -d --build Explanation: docker compose up -d → Runs containers in detached mode (in the background). If you previously had containers running, you may want to stop them first: docker compose down Then, rebuild and restart: docker compose up -d --build Now, your changes should take effect. Let me know if you run into issues! |
Same issue here but web rebuild fails with the below error. Hopefully this will be fixed in v1.0.2 next week.
|
Self Checks
Dify version
1.0.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
The Markdown table is too wide, causing the scrollbar to disappear and resulting in the data in the latter half not being displayed.
llm output data :
"下面是2025年1月山东地区的电价详情:\n\n| 电压等级 | 代理购电价格(元) | 容量补偿电价(元) | 上网线损费用(元) | 系统运行费用(元) | 政府性基金及附加(元) | 输配电价(元) | 需量电价(元) | 容量电价(元) | 尖峰时段电价(元) | 高峰时段电价(元) | 平时段电价(元) | 低谷时段电价(元) | 深谷时段电价(元) |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n| 不满1千伏 | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.2219 | - | - | 1.2669 | 1.1139 | 0.7568 | 0.3998 | 0.2977 |\n| 1-10千伏 | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.2069 | - | - | 1.2519 | 1.0989 | 0.7418 | 0.3848 | 0.2827 |\n| 35千伏及以上 | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.1919 | - | - | 1.2369 | 1.0839 | 0.7268 | 0.3698 | 0.2677 |\n| 1-10千伏 (两部制) | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.1491 | 38.4 | 24.0 | 1.1941 | 1.0411 | 0.684 | 0.327 | 0.2249 |\n| 35-110千伏以下 (两部制) | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.1341 | 35.2 | 22.0 | 1.1791 | 1.0261 | 0.669 | 0.312 | 0.2099 |\n| 110-220千伏以下 (两部制) | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.1191 | 35.2 | 22.0 | 1.1641 | 1.0111 | 0.654 | 0.297 | 0.1949 |\n| 220千伏及以上 (两部制) | 0.4003 | 0.0705 | 0.0122 | 0.0057 | 0.0272 | 0.1041 | 32.0 | 20.0 | 1.1491 | 0.9961 | 0.639 | 0.282 | 0.1799 |\n\n以上信息为不同电压等级和工商业类型的电价详情。如需了解更详细的信息,请告知具体的电压等级和工商业类型。"
✔️ Expected Behavior
❌ Actual Behavior
The text was updated successfully, but these errors were encountered: