mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
Quickly interacting with panel results in a blank screen #234
Reference in New Issue
Block a user
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?
Originally created by @Geitenijs on GitHub (Jan 7, 2025).
Current Behavior
When moving quickly inside the new client / admin area, for example digging into multiple folders at once or switching between Console, Files, Backups or whatever, the entire site will just turn blank. This is not something new with the latest beta but has been the case since the new UI was released.
See attached screen recording
https://github.com/user-attachments/assets/51b5bbd7-e07c-44ce-98e8-f6b9e14ff6b5
Expected Behavior
It should be able to handle that just like the old UI does.
Steps to Reproduce
I've noticed this on Safari 18.2, though Firefox 133.03 gives the same results. Not into Chrome so haven't tried that
Panel Version
1.0.0-beta17
Wings Version
1.0.0-beta9
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
No response
Is there an existing issue for this?
@rmartinoscar commented on GitHub (Jan 7, 2025):
Couldn't reproduce, are you using a proxy ?
@Geitenijs commented on GitHub (Jan 7, 2025):
Nope
@notAreYouScared commented on GitHub (Jan 7, 2025):
I think this is a limit of the hardware the panel is running on as I also cannot reproduce it
@Geitenijs commented on GitHub (Jan 7, 2025):
Definitely not the hardware. The old UI is very capable of handling this type of use. Plus, multiple Minecraft servers running buttery smooth + quite a bit of headroom indicates that my machine is capable of loading a webpage with some lines of text.
Maybe there's something wrong with the configuration, though I haven't changed anything myself. Ive been running Pelican since beta 10 I believe.
Also, I just tried it on the Pelican live demo and got the same result. On a different computer of mine by the way, so that's also ruled out.
https://github.com/user-attachments/assets/dd21aa31-b169-49be-bcfc-7c7ec0d49f21
@rmartinoscar commented on GitHub (Jan 7, 2025):
I tried on Windows, Linux & Mac
Chrome, Firefox, Safari and i couldn't reproduce even on demo
@Geitenijs commented on GitHub (Jan 7, 2025):
Then you're probably not doing the same thing as I am. I can reproduce it on any device as shown. Here's another example using my iPad
https://github.com/user-attachments/assets/c3fb5b71-5917-4ec4-8106-a57e13594b88
@NerdsCorp commented on GitHub (Jan 7, 2025):
It's a limitation of livewire, I sent this to @notAreYouScared via discord yesterday.
@NerdsCorp commented on GitHub (Jan 7, 2025):
I have been able to do it on the demo a few times now, if you click rapidly on any of the tabs it overloads livewire.
@Geitenijs commented on GitHub (Jan 7, 2025):
Interesting! Looking at their site which seems to be running on livewire too, I'm unable to overload it. So it should be something we can work around
https://livewire.laravel.com/docs/components
@NerdsCorp commented on GitHub (Jan 7, 2025):
Correction, with the merged PR of feature/vite I no longer have this issue.
@lancepioch commented on GitHub (Apr 11, 2025):
Looks like this is a library restriction, not much we can do unfortunately. Feel free to raise an issue with the parent library to see if limits can be dynamically updated.
@Geitenijs commented on GitHub (Apr 11, 2025):
I’m sorry, but if you read through the issue carefully, you’d see we’ve already tested this in several ways.
Livewires own website doesn’t have this issue. Besides, it is super trivial to reproduce on any Pelican Panel. I’m sure a lot of server owners working though files quickly would also run into this problem (just like I still do every day).
@rmartinoscar commented on GitHub (Apr 11, 2025):
Im 99% sure he was talking about Filament not Livewire
@Geitenijs commented on GitHub (Apr 11, 2025):
Whatever library it is, the new panel is not functioning normally due to this issue and it’s forcing me to stay on an older beta or to revert back to Pterodactyl.
@Geitenijs commented on GitHub (Apr 19, 2025):
@lancepioch How did you come to your conclusion and what are the next steps towards resolving this issue?
Besides looks, the new client area is super inconvenient to work with. Sluggish, just crashes when you want to get things done quickly, file uploads are an absolute nightmare and involve 5+ steps instead of simply drag&drop onto the viewer like in the old UI.
There's so much more, but then again it's in beta and it's fine for what it is. However, it shouldn't just throw a blank screen when interacting faster than a granny would, that's just terrible and I really don't understand why this is being swept under the rug. I'm definitely not the only one running into this issue.