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

the search input box of the document page cannot input #8060

Closed
5 tasks done
deific opened this issue Sep 6, 2024 · 2 comments · Fixed by #8065
Closed
5 tasks done

the search input box of the document page cannot input #8060

deific opened this issue Sep 6, 2024 · 2 comments · Fixed by #8065
Labels
🐞 bug Something isn't working

Comments

@deific
Copy link

deific commented Sep 6, 2024

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

0.7.3

Cloud or Self Hosted

Cloud

Steps to reproduce

image
1.On the document page of the knowledge base, the search input box cannot input

✔️ Expected Behavior

The search input box allows you to input and search for matching results

❌ Actual Behavior

the search input box cannot input

Copy link

dosubot bot commented Sep 6, 2024

Hello @deific! I'm here to help you with any bugs, questions, or contributions you have for Dify. Let's tackle this issue together!

I found a similar closed issue that might be relevant to your problem: Can not input params in tool test modal. This issue was resolved by a pull request: fix: can not input param value in tool test modal [1].

Additionally, there are several factors that might be affecting the input functionality of the search box:

  1. Event Listeners: The search input box has several event listeners attached, such as compositionstart, compositionend, keydown, keyup, input, and mousedown. If imeSessionInProgress is true, it might prevent input handling [2].

  2. CSS Styles: The input element has classes like bg-inherit, border-0, and outline-0, which could make the input less visible or appear disabled. The appearance-none class removes the default styling of the input element, which could also affect its visibility or functionality [3][4].

  3. JavaScript Logic: The useBoolean hook manages the focus state of the search box, and the onClick event handler on the search box's container prevents event propagation, which could interfere with input [5].

You might want to check these aspects in your implementation to ensure that the search input box is functioning correctly.

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added the 🐞 bug Something isn't working label Sep 6, 2024
@crazywoola crazywoola assigned JzoNgKVO and unassigned JzoNgKVO Sep 6, 2024
@crazywoola
Copy link
Member

Link #7782

@crazywoola crazywoola linked a pull request Sep 6, 2024 that will close this issue
12 tasks
@crazywoola crazywoola mentioned this issue Sep 6, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants