-
Notifications
You must be signed in to change notification settings - Fork 110
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
Improve behaviour with Algolia search #66
Comments
I think this would be solved by adding SSR support (#44) |
Great, you're already on it then 👍 Looking forward to see if that fixes this issue 🙂 |
One other thing: Would this be also fixed by #44 or is it a different problem? |
offset could be a different problem. Can you share a link to your site/repo so I can recreate the issue? |
You can see it here, but the repo's private. |
Did you fix the scroll offset somehow because it's not reproducible for me now. |
I think SSR should fix this, let me know if you try it out and problem still persists |
Feature suggestion
I suppose that most users that need a search bar will use the Algolia plugin provided by docusaurus.
Using this search, it can happen that you click on an API hit result, and it takes you to the right page, but not to the correct heading. Most probably because the page can take a bit too long to load, depending on your OAS file.
Here is an example. Notice that:
I understand that the load times are purely redoc-related and there's nothing this great plugin can do about it. But maybe we could have some kind of property to manage a timer until the browser tries to reach the anchor.
I'm not sure how to deal with this issue.
Any ideas?
The text was updated successfully, but these errors were encountered: