[Mainsite] New comment bugs noticed

[kouyo]

Hi everyone, Canary was updated with a bunch of fixes, I'll share the list here:

• Users without permission to comment can now create a forum thread for chapters again.
  • The context menu on the comment composer that used to have buttons related to forums has been removed.
  • To create a new forum thread, the button on the bottom of the comment thread is replaced with a "Create a thread in the forums" button.
• The comment count tooltip used to display "Show null comments" when there was no forum thread for the specified chapter. This has been fixed by removing the tooltip.
• The comment count widget on chapter and title cards used to only display the forum comments. Now it properly sums the comments on-side and in the forums.
• On very wide screens (a little more than 4k in width), the comments list wouldn't show in the reader comments sidebar. This is now fixed.
• On external chapters, the comment button would navigate you to the reader with the comments open. This wasn't particularly a bug, but the view certainly was awkward, due to the different way external chapters are shown in the reader if the user somehow lands directly to them. Now, the comment button next to chapters (and title cards) opens a designated sidebar with the comment thread. Users on the forums also requested that they don't want to accidentally mark a chapter as read when they only want to read comments, so this change should address their concerns as well.

We appreciate everyone's patience while we're working on fixing bugs

 

[grrman]

money

Yeah I don't get that part. How does removing the forum link make them money?

 

[panzerkampfwagyu]

Yeah I don't get that part. How does removing the forum link make them money?

I guess less time wasted on it being a pain in the ass?

 

[detarameMangadex]

Hi everyone, Canary was updated with a bunch of fixes, I'll share the list here:



We appreciate everyone's patience while we're working on fixing bugs

Thanks devs for the fixes, and thank you for the announcement :D

 

[Hicleric]

I'm not able to launch comments from the update page (using DDG on Android) on Canary. Launching chapters works fine and I can open comments from the series page, so it seems like this bug is specific to the updates page.

I can confirm that I had an option to create a new forum thread as Group 3. Not 100% certain if I was able to actually create it since it didn't give me any indication it was successful--just kind of sat there spinning for a while with no popup or redirect. The thread was created when I checked in parallel, but it's possible somebody else created it in the interim.

Really appreciate that comments doesn't open the chapter now, too. Now all we need is a Comment button sitting next to the Next Chapter button in the reader (because if you want to drive engagement, that is the logical place for it) and I'll be satisfied with the current implementation

 

[Angry_Panda]

Two notes:

I'm not able to launch comments from the update page (using DDG on Android) on Canary. Launching chapters works fine and I can open comments from the series page, so it seems like this bug is specific to the updates page.

The comment icon isn't working from either Updates or Latest Updates (or, if you're an uploader, from the Upload page) - that is on the list in the early access channel on the Discord as something that needs ironed out.

I can confirm that I had an option to create a new forum thread as Group 3. Not 100% certain if I was able to actually create it since it didn't give me any indication it was successful--just kind of sat there spinning for a while with no popup or redirect. The thread was created when I checked in parallel, but it's possible somebody else created it in the interim.

Also a known issue when you create a new forum thread from outside the reader, and also on the list. It does in fact create the thread, but currently doesn't properly confirm back to the popup.

 

[asfhoiasfjoiasfjpi]

Yeah I don't get that part. How does removing the forum link make them money?

you have to look past the paywall comments first
not a particularly complicated take

 

[Hicleric]

Another odd bug that cropped up on Canary (should I be posting these here? I don't see the EA channel in Discord) affecting my ability to scroll, which I suspect is caused by the comments overlay not being removed properly when using my browser's back function

1) Navigate from a page to a series page
2) Open the comments popup for a chapter (note: NOT the series comments tab) but don't close it with the close button.
3) Use the back function to return to the original page (tested on updates and reading history)
Result: I'm no longer able to scroll successfully (scroll bar pops up, but seems to hit a boundary) until I navigate to a new page (not via the page # navigation) or refresh.

Only tested on DDG on Android.

Yes, I could get around this by closing the comments popup first but I ain't letting go of 30 years of muscle memory like that.

 

[grrman]

you have to look past the paywall comments first
not a particularly complicated take

I hadn't seen that yet for some reason.
Not sure why not, but hey what else isn't broken right now.

 

[Hicleric]

Now that the new implementation has stabilized...

Whatever the fix was also seems to be increasing load times on series' pages, maybe since there's more chapter data (via a vis comments) through the API now? At least the # of comments graphic next to each chapter tends to lag for a couple of seconds after the rest of the page has finished loading.

 

[shinya78]

At least the # of comments graphic next to each chapter tends to lag for a couple of seconds after the rest of the page has finished loading.

Noticing this as well, and sometimes clicking the chapter comments button to bring up just the comments doesn't work. I had to refresh the title page a few times just to get it to work. It has yet to fail on me when doing it at Home page though.

If when refreshing a Title Page, and the Console gives me these:

TypeError: can't access property "emitsOptions", r is null

Object { result: "ko" }

This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see [firefox url] for further details and to join the discussion on related tools and features!

Then clicking on the button to bring up the comments will fail.

Console then returns me these when clicking the button fails on the Title Page:

TypeError: can't access property Symbol("_vtc"), e is null

TypeError: can't access property "emitsOptions", r is null

TypeError: can't access property "emitsOptions", r is null

This is on the latest Firefox.

 

[Hicleric]

I noticed the slowness on Canary but chalked it up to "different server".

I've had a handful of instances where opening the comments panel still moved a chapter to read (and my reading history) but I'm not able to do it reproducibly. Will update if I figure out how.

 

[boursk]

Noticing this as well, and sometimes clicking the chapter comments button to bring up just the comments doesn't work. I had to refresh the title page a few times just to get it to work. It has yet to fail on me when doing it at Home page though.

If when refreshing a Title Page, and the Console gives me these:



Then clicking on the button to bring up the comments will fail.

Console then returns me these when clicking the button fails on the Title Page:



This is on the latest Firefox.

This should be fixed on canary right now.

 

[shinya78]

This should be fixed on canary right now.

I'm not getting the errors on the live version anymore. The button now always opens the comments as intended.

---

Although, I'm not sure if this has something to do with the new changes...
You don't regain the ability to switch pages using your keyboard's arrow keys if you close the menu bar. Clicking somewhere inside the reader fixes this and return the function back, but so did closing the menu bar before the changes.

---

Side note, does any one else's status bar start freaking out when you click your avatar while inside the reader to bring out the profile_container?

It starts going back and forth displaying mangadex.org/user/me and that specific chapter's forum thread's url

It can also prevent you from logging out directly from the reader as the profile_container will immediately scroll back up if you scroll down far enough.

 

[boursk]

I'm not getting the errors on the live version anymore. The button now always opens the comments as intended.

Yes, the hotfix went live not too long after my last post. I didn't see a message from when that happened, so I didn't have a trigger to amend my post.

 

[shinya78]

Side note, does any one else's status bar start freaking out when you click your avatar while inside the reader to bring out the profile_container?

It starts going back and forth displaying mangadex.org/user/me and that specific chapter's forum thread's url

Same thing happens when logged out. Something recent must've caused this to occur.

edit:
Status bar will not freak out if the chapter does not have a forum thread created yet.
Profile_container scrolling back up by itself will prevent you from reaching the sign-out button if your screen is small enough.

 

[Chizan]

What's with the disappearing comment numbers in the right-hand column on older chapters? The comments are still there if you click though.

 

[BestBoy]

disappearing comment numbers

Ya the field where they'd normally be is slowly blinking. Maybe something on the backend is having trouble?

 

[Chizan]

Ya the field where they'd normally be is slowly blinking. Maybe something on the backend is having trouble?

Yeah, now the whole site seems to be glitching..

 

[DrDeltaDex]

Soo I’m not sure if I’m having a different comment prob then everyone else, but the main site and all my lists keep reloading after one page every few seconds because of the new comment box…I can barely scroll because it pulls up a blank comment box from a random manga I’m not even on and I can’t close it…