-
Notifications
You must be signed in to change notification settings - Fork 11.7k
Misc. bug: The web UI of llama-server is not displaying correctly. #13428
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
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
It's a browser-specific bug. You should try another browser, or try disabling plugins that may conflict with website's display |
I'm using Microsoft Edge, which should be a widely used browser. I'm not familiar with web front-end, but I just tried something myself—for example, the regenerate button: <button class="btn-mini show-on-hover w-8 h-8 flex items-center justify-center"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="1.5" stroke="currentColor" aria-hidden="true" data-slot="icon" class="h-4 w-4"><path stroke-linecap="round" stroke-linejoin="round" d="M16.023 9.348h4.992v-.001M2.985 19.644v-4.992m0 0h4.992m-4.993 0 3.181 3.183a8.25 8.25 0 0 0 13.803-3.7M4.031 9.865a8.25 8.25 0 0 1 13.803-3.7l3.181 3.182m0-4.991v4.99"></path></svg></button> The button appears when removing |
Then I noticed that .show-on-hover {
opacity: 0;
} It seems like some "dynamic opacity change on hover" code isn't executing properly. |
Can you simply try other browsers to see it's the same? If it only happens on Edge, we can simply adds CSS rule to make the button always show on Edge |
Name and Version
build: 5335 (d891942) with MSVC 19.43.34810.0 for x64
Operating systems
Windows
Which llama.cpp modules do you know to be affected?
llama-server
Command line
Problem description & steps to reproduce
A simple issue: This PR made some UI changes, but some buttons aren't displaying correctly on my end (though they remain clickable).
First Bad Commit
No response
Relevant log output
The text was updated successfully, but these errors were encountered: