A user, MikeNolan, reports a bug where the group request page in Discourse shakes when loading, particularly when navigating between pages. The issue is intermittent and occurs in Microsoft Edge on a Windows 11 laptop. zogstrip suggests a video would help, and MikeNolan attempts to share one, which is later edited into the post by JammyDodger after removing sensitive information. Moin explains that .mov files don’t work with the video component and suggests uploading them as regular files. j.jaffeux provides a reproducible scenario involving scrolling at the end of the page while loading, noting it might be related to debouncing or server responses. The issue is considered low priority, but a fix has been proposed in a pull request Lhc_fl links to.
It doesn’t happen every time I click on the groups tab to see if there are unfulfilled requests to join a group, but sometimes when it brings up the request the box with the message shakes up and down until I navigate to another page.
Don’t know how I can reproduce it or even show how it appears on our Discourse-hosted site. I suppose I could take a video of it on my iPhone. 
FWIW, I’m accessing it using Microsoft Edge on a Dell WIn 11 laptop.
Having a video would definitely help 
Group requests aren’t that frequent, but the next time I see this problem I’ll try to get a video of it.
I’m trying to post a video of the shaky screen issue but it doesn’t seem to be working, should I try emailing it to someone?
Jammy edit: Shared privately due to potentially sensitive info
I think I’ve managed to edit the video into your post. 
Edit Just noticed a bit of PII in there so have copied it over into a whisper.
What did you have to do to get the video to work, is it something that went wrong on my end?
The insert-video component does not work with .mov
I think you can upload .mov like other files instead of using the video button provided by the component
I got a fairly consistent repro. You need to scroll up and down multiples times after reaching the end of the page while the loading indicator is showing.
I didn’t dig the code yet, it might be related to 429 or just debouncing. The cases where you have it “naturally” are probably due to a specific size of the window which might create this loop of reached bottom/didn’t reach/reached bottom/didn’t reach…
We might look at this at some point; but this is fairly low priority.
Thanks for the good catch! This PR should fix it:
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.