I tested this out and it seems to work quite well. Text size is correct, and images render correctly and don't cause weird resizing and snapping issues I was experiencing with the previous renderer.

Some follow up notes from testing:

• If the last character of a line is italicized, it will be cut off. For example, if a comment is deleted, the d will appear as an a.
• Images are unloaded if they go off screen
• Images sharing a line with text do not have sufficient padding with that text. While this is probably correct for markdown, there should probably be some effort on the app's side to make it look better, by inserting additional newlines before and after pictures if they aren't there already.
• Sometimes images are very small and effectively unviewable.
• I had to update proguard rules on my local branch and I think this PR was responsible since it is the only one changing dependencies.

Here is an excellent thread for testing: https://beehaw.org/post/433016

Thanks for the feedback @twizmwazin

I found the issue / fix for the very small pictures. I will take a look at the other items soon

Actually the best option will be to use image-coil as the backend. Testing it now with my other fix seems to work very well. No image unloading.

Will do more testing and try and apply the same preview etc we use for post images.

Did you look at this PR at all? #274

RichText material 3 seems to be the best future-proof option for markdown rendering... I just couldn't get images working properly with it. IMO it would be better to work on that directly to add better image support, since that would positively affect all jetpack-compose projects that need markdown.

@dessalines I will take a look.

So far I have updated the pull request with the coil implementation. So far it works pretty well (with limited testing)

Apologies if i butchered the PR. Its my first stab at doing it "properly"

Its no problem, I should be able to get to this tomorrow.