Images can no longer be directly attached to posts or comments. Even though the Posting Guidelines and Creating Great Ideas pages do not make any mention of mention of Pictures being removed or being no longer allowed, the functionality seems to have been removed between late 2022 and early 2023  ^{Archived Sep 10, 2024.}

Steps to reproduce (Attaching an image to a post):

1. Navigate to the New Post page on the Minecraft Feedback site.
2. Log in with your Microsoft Account if you are not already.
3. Look at the options available on the toolbar of the "Details" text box.
4. Drag and drop an image from a file manager to the text box.

Steps to reproduce (Attaching an image to a comment):

1. Navigate to any post with open comments on the Minecraft Feedback site (Ex: Bedrock Editor Icon)
2. Click on the "FEEDBACK LOGIN" button to log in with your Microsoft Account if not already.
3. Click on the textbox located under the subtitle "Post a new comment:"
4. Look at the options available on the toolbar of textbox
5. Drag and drop an image from a file manager to the text box.

Expected Result:

The "Insert Image" button is still in the toolbar, and located between the "Insert/Edit link" and "Quote" buttons. Dragging and dropping an image onto a text box attaches it to the post or comment.

Observed result:

The "Insert Image" button is missing from the toolbar, and Images can no longer be inserted in both posts and comments if one tries to drag and drop an image onto the text box.

Notes:

While the functionality has been removed from the initial interface, an image can be inserted while editing a post or comment by dragging and dropping the image onto the text box. In addition, there have been multiple occasions (Ex: Unique Editor Icon, Bundle Enchantments, Tooltip Opacity, OreUI Player Profile, Turtle Helmet Blocks Mace, Hoppers Access Crafters) where comments and posts with images have been approved by moderators even after the disappearance of the "Insert Image" button, so this is definitely NOT a moderation issue. The issue affects both Google Chrome (version 131.0.6778.205) and Microsoft Edge version (131.0.2903.112) as of December 30, 2024.