[Mainsite] Blank/Non Existant Comment Thread lags library/MDlists, reloads page after I scroll down, Breaks the entire site

[DrDeltaDex]

Posted about this in another thread, but I’ll give a basic description of this bug here: On my phone (on Safari) when I look at my library or a list of any kind on mobile, a random blank comment section appears at the bottom of my screen from a manga I haven’t clicked on (or one that may not even be in my library). I have never had this pop up before, it only showed up this morning and it happens every time I go to the library/MDlist on my phone


Said comment section can’t be clicked on, interacted with, or closed in any way, and reloads my page every few seconds after I scroll down. After a few times of reloading the page it shits out an error message or says "A problem repeatedly occured on mangadex.org/titles/follows/ or the site and continues to break the site every time I try to reload the page myself. I can’t scroll, I can’t see any list…can someone make a setting to turn this off or remove this somehow? I can’t tell if this is a new bug or part of another problem.

How to Reproduce the Problem:

1. Open Mangadex site on the most recent version of Safari on a recent IPhone

2. Swipe Down, Page reloads itself (Regardless if you are on data/low power mode/Wi-Fi)

 

[Angry_Panda]

Couple things that would help diagnose this:

What OS (version)?
What browser (version)?
Any extensions/plug-ins being used?
Have you tried clearing the cache for the site?

 

[Hicleric]

'How-To: Write Better Bug Reports' https://forums.mangadex.org/threads/how-to-write-better-bug-reports.2001411/

 

[Dverin_Oshiban_Duren]

I kinda have this problem as well. Using Firefox (148) in Android, when I scroll, the top part of the new comment section which includes just the chapter title pops up from the bottom of the screen for a bit. Doesn't cause any other serious problems though.
The chapter is usually one which is somewhere on the page.
Works in incognito as well but not on chrome.
Been having this issue since the update which was meant to fix the comments and had this problem on canary as well when I used it 2 days ago.