Moderation -- raw markdown editor too small

AI-generated summary

The discussion on the moderation queue highlights a bug where the raw markdown editor is too small and cannot be expanded on shorter posts in the review detail page, particularly affecting Firefox on MacOS. j127 first noticed the issue, later clarifying that URL parsing in the review system appears to be broken, with examples showing incorrect URL formatting. j127 and j127 provide visual evidence of the problem, including a malformed URL and a TikTok link issue. kris.kotlarek acknowledges the report, confirms the bug, and states it has been fixed in a recent pull request kris.kotlarek.

It looks like a recent update might have change the moderation queue detail page so that the editor on that screen is now very small on shorter posts when in raw markdown mode, and it can’t be expanded. (Firefox 143.0.1 on MacOS Sequoia 15.6.1)

Edit: actually, I’m not sure about this. I’ve already approved everything for this morning though and can’t double check right away. Try switching back and forth between WYSIWYG and raw markdown, and the preview doesn’t disappear for the WYSIWYG so there are two versions on the page. I think the monospace font also disappeared in the raw markdown editor, so I’m looking into that now.

2 Likes

Something else seems to be wrong with items in review on routes like /review/1234

Here’s how a URL is moderation is being parsed:

Here’s the URL: https://www.johndcook.com/blog/2023/03/03/conway-factoring/

It looks fine after the post is approved, but it’s broken in the review item detail. The first part (https://www.johndcook.com/blog/) turns into a link, but the rest of the path (2023/03/03/conway-factoring/) isn’t counted as part of the link.

Here’s another one from TikTok, only in the review detail view:

tiktok@2x

(The word “video” is a watched word, if that matters.)

It looks fine once the post is approved.

Thank you for reporting this issue. I reproduced that bug in my local environment and will try to fix it this week.

1 Like

Thank you again. It was fixed in this PR

https://github.com/discourse/discourse/pull/36036

3 Likes