langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Tapping the added button tag does not send a message. #14569

New Issue
Closed
opened 2026-02-21 19:17:50 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:17:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @Miranofuu-Dodoria on GitHub (Jun 11, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.4.2

Cloud or Self Hosted

Cloud

Steps to reproduce

feat: support button in markdown #9876, the content described in the data-message cannot be sent after tapping the button.

Until v1.4.1, the message was sent after the button was tapped, but as of v1.4.2, the message is not sent even if the button is tapped.

✔️ Expected Behavior

Message is sent after tapping the button as in v1.4.1.

❌ Actual Behavior

feat: support button in markdown #9876 and not the same behavior.

Originally created by @Miranofuu-Dodoria on GitHub (Jun 11, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.4.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce feat: support button in markdown #9876, the content described in the data-message cannot be sent after tapping the button. Until v1.4.1, the message was sent after the button was tapped, but as of v1.4.2, the message is not sent even if the button is tapped. ### ✔️ Expected Behavior Message is sent after tapping the button as in v1.4.1. ### ❌ Actual Behavior feat: support button in markdown #9876 and not the same behavior.
yindo added the 🐞 bug label 2026-02-21 19:17:50 -05:00
yindo closed this issue 2026-02-21 19:17:50 -05:00
yindo commented 2026-02-21 19:17:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 11, 2025):

This issue is related to the "support button in markdown" feature, specifically with the data-message attribute not working as expected in v1.4.2—others have reported that tapping the button no longer sends the message, even though it worked in v1.4.1. The button component itself still fires its onClick event as expected, and the message-sending logic in the chat input area hasn't changed in a way that would obviously break this feature. There are no explicit changelog notes or code changes documented between v1.4.1 and v1.4.2 that explain this regression, but the problem appears to be recognized by maintainers as related to the markdown button feature and its integration with the message send flow (source).

If you need to reference the implementation, the button is handled in web/app/components/base/button/index.tsx, and the message send logic is in the chat input area and operation components. No workaround is documented yet, but the regression is confirmed.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jun 11, 2025): <!-- Answer --> This issue is related to the "support button in markdown" feature, specifically with the `data-message` attribute not working as expected in v1.4.2—others have reported that tapping the button no longer sends the message, even though it worked in v1.4.1. The button component itself still fires its `onClick` event as expected, and the message-sending logic in the chat input area hasn't changed in a way that would obviously break this feature. There are no explicit changelog notes or code changes documented between v1.4.1 and v1.4.2 that explain this regression, but the problem appears to be recognized by maintainers as related to the markdown button feature and its integration with the message send flow [(source)](https://github.com/langgenius/dify/issues/15400). If you need to reference the implementation, the button is handled in `web/app/components/base/button/index.tsx`, and the message send logic is in the chat input area and operation components. No workaround is documented yet, but the regression is confirmed. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9deb23c4-928c-4db5-87b6-2cd00c6054bd?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/20932)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14569
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?