-
Notifications
You must be signed in to change notification settings - Fork 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
Inconsistent Search Results Behaviour #9135
Labels
Comments
daixiang0
changed the title
<what happen when you do on which document project>
Inconsistent Search Results Behaviour
Apr 26, 2021
Could you try v4.0.0b1? It contains a fix #8070 for short terms like "ip". |
I try install it but fail:
Since I need sphinx-tabs, what can I do? Please help me @tk0miya , thanks. Is it possible to release a bugfix version for Sphinx3? |
Sphinx Tabs will soon get updated for Sphinx 4 |
Happy to hear it! @Daltz333 could share detail plan, we want it deeply! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I noticed when searching for ip tagging, that I could only find the page when i matched text in the qualified names referenced on the page. Other pages I could find by matching any text on the page.
To Reproduce
Steps to reproduce the behavior:
I reproduced the below behaviour on firefox, chrome, and safari. I did not test on all versions, but reproduced using latest, 1.17.1, 1.16.1, and 1.13.1
in the search field of the docs enter any of these terms: "ip tagging", "ip tag", "ip" and note the results.
enter "iptag" and note the results.
enter "kafka broker", "kafka", "kafka b", "emitting results", then note results.
The first set of terms will not bring up the ip tagging page. "iptag" will return the page by matching on the qualified names in the page. Any of the last terms will bring up the correct kafka broker page among its results.
Expected behavior
I can get results with
iptag
input.Your project
https://github.com/envoyproxy/envoy/tree/main/docs
The text was updated successfully, but these errors were encountered: